Network Supervisor's Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ Network Supervisor's Toolkit / Network Supervisor's Toolkit.iso / novell / rlit93 / 10feb93l.net next >

Wrap

Text File | 1996-07-10 | 506.8 KB | 12,504 lines

FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Resolving I/O and IRQ Conflicts DOCUMENT ID#: FYI.P.6054 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6012 and FYI.P.6013 SYMPTOM NA ISSUE/PROBLEM Resolving I/O and IRQ Conflicts I/O Conflicts The Ethernet, ARCnet, or other network board will need to use a unique I/O address. The following table shows some possible conflicts. Column one shows the range from 200 to 3E0 (hex). Column two shows some possible conflicting devices. Select an I/O address that best fits your configuration; however, be aware that this table is generic. If problems persist, consult the documentation of your specific system. It is also possible to get a listing of your I/O addresses with a computer utility program. ┌──────────────┬─────────────────────────────────────┐ │ I/O Address │ Potential Conflicting Devices │ ├──────────────┼─────────────────────────────────────┤ │ 200 │ Game controller /Joystick (200-20F) │ ├──────────────┼─────────────────────────────────────┤ │ 220 │ Novell Network Keycard │ ├──────────────┼─────────────────────────────────────┤ │ 240 │ │ ├──────────────┼─────────────────────────────────────┤ │ 260 │ LPT2: (278-27F) │ ├──────────────┼─────────────────────────────────────┤ │ 280 │ LCD display on Wyse 2108 PC │ ├──────────────┼─────────────────────────────────────┤ │ 2A0 │ │ ├──────────────┼─────────────────────────────────────┤ │ 2C0 │ │ ├──────────────┼─────────────────────────────────────┤ │ 2E0 │ COM4:, GPIB-Adapter 0 (2E1) │ │ │ COM2:, Data acquisition (300-31F) │ ├──────────────┼─────────────────────────────────────┤ │ 300 │ │ ├──────────────┼─────────────────────────────────────┤ │ 320 │ XT Hard Disk interface (320-32F) │ ├──────────────┼─────────────────────────────────────┤ │ 340 │ │ ├──────────────┼─────────────────────────────────────┤ │ 360 │ LPT1: (378-37F) │ ├──────────────┼─────────────────────────────────────┤ │ 380 │ SLDC/Sec Bi-Sync interface (380 │ ├──────────────┼─────────────────────────────────────┤ │ 3A0 │ Primary Bi-Sync interface (3A0-3A9) │ │ │ Monochrome display (3B0-3BB) │ ├──────────────┼─────────────────────────────────────┤ │ 3C0 │ EGA display control (3C0-3CF) │ │ │ CGA display control (3D0-3CF) │ ├──────────────┼─────────────────────────────────────┤ │ 3E0 │ COM3: (3E8-3EF) │ │ │ Floppy disk controller (3F0-3F7) │ │ │ COM1: (3F8-3FF) │ └──────────────┴─────────────────────────────────────┘ IRQ Conflicts A unique interrupt line (IRQ) must be assigned to your network board. Each manufacturer's network board is unique in the available interrupts it offers (refer to the network board's manual to determine its interrupt options). The following table may help in selecting an interrupt option that is not currently being used in your system. It is also possible to get a specific reading of your interrupts from a computer utility program. ┌───────┬────────────┬──────────────────┐ │ IRQ │ XT │ AT (286,386,486) │ ├───────┼────────────┼──────────────────┤ │ 0 │ │ TIMER OUTPUT 0 │ ├───────┼────────────┼──────────────────┤ │ 1 │ │ KEYBOARD │ ├───────┼────────────┼──────────────────┤ │ 2 │ EGA/VGA │ EGA/VGA │ ├───────┼────────────┼──────────────────┤ │ 3 │ COM2 │ COM2 │ ├───────┼────────────┼──────────────────┤ │ 4 │ COM1 │ COM1 │ ├───────┼────────────┼──────────────────┤ │ 5 │ HARD DISK │ LPT2 │ ├───────┼────────────┼──────────────────┤ │ 6 │ │ FLOPPY DISK │ ├───────┼────────────┼──────────────────┤ │ 7 │ LPT1 │ LPT1 │ ├───────┼────────────┼──────────────────┤ │ 8 │ │ REAL TIME CLOCK │ ├───────┼────────────┼──────────────────┤ │ 9 │ │ │ ├───────┼────────────┼──────────────────┤ │ 10 │ │ │ ├───────┼────────────┼──────────────────┤ │ 11 │ │ │ ├───────┼────────────┼──────────────────┤ │ 12 │ │ │ ├───────┼────────────┼──────────────────┤ │ 13 │ │ COPROCESSOR │ ├───────┼────────────┼──────────────────┤ │ 14 │ │ HARD DISK │ ├───────┼────────────┼──────────────────┤ │ 15 │ │ │ └───────┴────────────┴──────────────────┘ Note: For best results, you should try using a free interrupt line. If the chart shows that you are using all possible interrupts, it is possible that your Ethernet or other network board may use an interrupt that is already being used. For example: many programs do not address LPT1 on the interrupt level; hence, if you have no free interrupts, it is possible to assign two functions to the same interrupt. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite Patch Release DOCUMENT ID#: FYI.P.6087 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6041 SYMPTOM NA ISSUE/PROBLEM NetWare Lite Patch Release Novell has released eleven patches that address various NetWare Lite issues. These patches can be obtained through CompuServe or through Novell directly. CompuServe A free CompuServe membership can be obtained by dialing (800)848-8199 in the U.S. and (614)457-0802 outside the U.S. (ask for Representative 200). CompuServe will provide NetWare Lite users with fifteen dollars worth of credit toward online services at no charge. To get the files from CompuServe, do the follow procedure: 1. Type GO NOVLIB 2. When in NOVLIB, enter into library one or ten. 3. Download NWL005ZIP. (This ZIP file contains the NetWare Lite patches.) Note: You must have PKUNZIP.EXE to unzip NWL005.ZIP. If you do not have PKUNZIP.EXE, you can get it from CompuServe. It is located inside PKZ110.EXE, which is another file that must be downloaded. a. To download PKZ110.EXE, create a directory called PKZIP (either on floppy diskette or on your hard drive). b. Go to library 15 of NOVLIB and download PKZ110.EXE. c. Then, move PKZ110.EXE into the PKZIP directory. d. Type PKZ110 PKZ110.EXE will create PKUNZIP.EXE (and other programs that can be used for archiving functions). 4. When you have PKUNZIP.EXE, you can unzip NWL005.ZIP. 5. Put NWL005.ZIP into the PKZIP directory. 6. Next, type the following: PKUNZIP NWL005.ZIP <path where you want the files to be copied to> The patch files will be copied to the directory that you specify. Novell recommends that you copy them to a floppy diskette. This way, you will have a copy of the patches in a distinct and identifiable place. Novell If you want the patches but cannot access CompuServe, call Novell at (801)429-5483 and request the NetWare Lite Patch Disk. It will be sent to you through U.S. Mail and will take from four to seven days to arrive. The following is a list of the files that will be sent to you. (Note that these are the same files that are contained in the NWL005.ZIP file.) 5E03 PAT 877 11-26-91 5:55p CGADSPLY PAT 1173 01-27-92 2:30p KEYCLOCK PAT 2537 01-17-92 10:40a LOSTRESP PAT 1747 11-26-91 1:36p NWL005 DOC 20475 07-13-92 3:20p PBIOS17 PAT 1474 12-17-91 1:57p PCPS PAT 316 01-27-92 3:03p PCPS ZIP 6460 02-06-92 10:38a PRNLPT1 PAT 1705 01-08-92 5:08p PTIMEOUT PAT 1170 11-22-91 3:37p RDCACHE PAT 1052 11-22-91 3:18p UPATCH EXE 19690 01-16-92 9:35a WRBEHIND PAT 1178 11-22-91 3:37p TASKFIX PAT 890 06-11-92 9:45a General Information The files listed below are previous patches to NetWare Lite. All of them are superseded by the patches contained in NWL005.ZIP. NWL004.ZIP NWL003.ZIP NWL002.ZIP NWL001.ZIP Four of the patches contained in NWL005.ZIP (PBIOS17.PAT, PRNLPT1.PAT, 5E03.PAT, and CGADSPLY.PAT) may not improve the performance on your system but will not decrease the performance either. These four patches are for specific hardware or applications. Review the corresponding section of this document to determine if you would benefit from any of these four patches. Installation Please be sure to backup your old SERVER.EXE and CLIENT.EXE before you attempt to apply the patch. Backing up your data files would also be wise. To install the patches, place the disk where the patch files reside into drive A: and type UPATCH. This must be done to all machines on your network. Please read the documentation that accompanies NWL005.ZIP for details on the installation. The following information is contained in the NWL005.DOC file and is included in its original form. Included are the patch name, date, and the file that is affected by the patch (such as SERVER.EXE), and problems (with accompanying symptoms) that each patch deals with. PATCH DESCRIPTIONS ============================================================ ===== 5E03.PAT NetWare Lite Client DOS 5E03 invalid parameter patch Patch Date: November 26, 1991 File: CLIENT.EXE Checksums: 55F, 509, 57 Problem: When DOS-interrupt 21h, function 5E03 (Get Printer Setup String), is used on a disk device, the client returns an error code of 1 (invalid function). Software from Computer Associates International, Inc. expects an error code of 87 (invalid parameter). Symptoms: If you are running software from Computer Associates, you may note that networking features do not work. CAI software expects a different error code on function 21, 5E03 than NetWare Lite currently returns. ============================================================ ===== CGADSPLY.PAT NetWare Lite Server CGA Display Patch Patch Date: January 27, 1991 File: SERVER.EXE v1.00 Checksums: 410, 4D1, 3FF, 49F, 1B0, 1B0 Problem: The problem occurs with any PC with a CGA adapter running a NetWare Lite v1.00 SERVER. When pressing <Ctrl>+<Alt>+<Del> or <Alt>+<Shift>+<N>, you should see a popup display with options; instead you see a blank screen. It functions as expected; however, the display is blank. Symptoms: This problem is specific to CGA display adapters. It is only experienced when a user presses <Ctrl>+<Alt>+<Del>, <Alt>+<Shift>+<N>, or when one of the popup display screens is encountered. ============================================================ ===== KEYCLOCK.PAT NetWare Lite Server 1.00 Keyboard Clock Conflict Patch Patch Date: January 17, 1992 File: SERVER.EXE version 1.00 Checksums: 6F8, BC9, 57C, EB3, 6F9, B54, 2AC, D10, 6F8, BC9, 3E8, EB3 Problem: While typing at the server keyboard the server pauses. This is most likely to occur when the server is under heavy load, such as a client performing an XCOPY to and from the server. Symptoms: You may have this problem if you see the server pause for 70 seconds or longer. Most people may think the server is hung because no foreground activity is occurring and the server is not answering requests from clients. However, the server does eventually return; the foreground activity resumes; no time is lost on the system clock; if the client retries its request, the response is sent. The slower your hardware, the more likely you are to see this problem and the longer the pause is likely to last. ============================================================ ===== LOSTRESP.PAT NetWare Lite Server lost response patch Patch Date: November 26, 1991 File: SERVER.EXE Checksums: D4D, 17B8, 416, 3A3, D4D, 17B8 Problem: The last function result is not saved correctly in the server's connection table. This results in nonreproducible functions (like OPEN FILE) being reproduced at the server when a server response packet is lost. This ends up exhausting the server's resources after a long period of sustained activity. Symptoms: You may have this problem if DOS or your application reports the error "Too many open files" after running continuously for several hours or days. Another symptom that occurs after continuous operation is that one of the machines freezes or reports a DOS function failure. ============================================================ ===== PBIOS17.PAT NetWare Lite Server Printer BIOS Get Status Patch Patch Date: December 17, 1991 File: SERVER.EXE Checksums: 18F0, 19A8, 18F0 Problem: The ROM BIOS for some computers destroys the contents of a register when the server read the status of the printer. When the server attempts to print a character, null, or other, invalid characters appear instead of the desired file. Symptoms: Print job does not print or is printed in garbled form. This problem can only happen if the server port is a parallel port. ============================================================ ===== PCPSxxxx.PAT NetWare Lite Network Printer Characters Per Second Patch Patch Date: January 17, 1992 File: NetWare Lite Server printer port configuration file Checksums: 55, CA, C9, 92, 24, 47 Problem: The NET utility does not allow Network Printers to have characters per second set any higher than 2048. Symptoms: Large print jobs take considerably longer (up to four times) when printed using a Network printer than when using a local printer. Foreground processing at the server may be slowed during printing after applying this patch. Note: The NET Utility does not properly calculate the changes this patch makes. Therefore, any display of the characters per second will not be accurate. To view the current setting, run the appropriate batch file; read the value; then select option 7 to make no change. ============================================================ ===== PRNLPT1.PAT NetWare Lite Client PRN and LPT1 merge patch Patch Date: January 8, 1992 File: CLIENT.EXE Checksums: 59A, 26D, E13, 413, 61c, 9A0, 59A, 26D, E13 Problem: Applications that intermingle writes to the printer using PRN: and LPT1: produce incorrect printouts. This is because the NetWare Lite client treats the captures of PRN: and LPT1: as separate captures. This patch forces the two captures into a single capture. This is a known problem with the Lacerte Tax Application version 11.0322. Symptoms: You may have this problem if you see corrupt printing. ============================================================ ===== PTIMEOUT.PAT NetWare Lite Client printer (PRN) timeout patch Patch Date: November 22, 1991 File: CLIENT.EXE Checksums: 1166, 50B, 1166 Problem: Client program fails to imply a print job timeout on a PRN port capture. Symptoms: If you print from an application, but the job does not start printing at the server until you exit the application, you may have this problem. Check to see if the banner page on the delayed print job indicates that the "Client printer port or filename" is "PRN capture." If so, this is an indication that the application is using PRN and not LPT1 for its printing. Programs compiled under Clipper are known to print through PRN thus are affected by this problem. ============================================================ ===== RDCACHE.PAT NetWare Lite Server read-ahead cache patch Patch Date: November 22, 1991 File: SERVER.EXE Checksums: BF0, 3EF, BF0 Problem: The server makes an invalid entry in the read-ahead cache when a read is issued past the end of the file. The invalid entry contains no data and could be returned after the file is extended and a subsequent read is made to the same area of the file in a short time. Symptoms: If you have a database program that incorrectly reports that the end-of-file has been encountered or exhibits problems reading or updating the index file for a database, you may have this problem. Programs compiled under FoxBase and Clipper are known to make I/O call sequences that result in the error. ============================================================ ===== WRBEHIND.PAT NetWare Lite Server write behind patch Patch Date: November 22, 1991 File: SERVER.EXE Checksums: D1E, 3B0, D1E Problem: The server write-behind offset is corrupted when a packet is lost on the wire. This results in data being written in the wrong place in a file when the underlying network drops a packet. This only occurs with certain combinations of buffer sizes, application-write sizes, and write offsets. Symptoms: If you have file data corruption under particularly heavy load or if you have a particular machine or particular application that appears to corrupt data when it is used, you may have this problem. ============================================================ ==== TASKFIX.PAT NetWare Lite Client DOS task count patch Patch Date: June 11, 1992 File: Client.exe Checksums:3 6F, 2D9, 120 Problem: When running certain applications on a NetWare Lite client, the DOS End-of-Task command is missed and never sent to the server. This results in having dangling tasks on the server that cannot be removed until the client does a NET LOGOUT or NET LOGIN to clear the connection. In most cases, this bug should not cause serious problems if the task count on the server is set to the maximum (200). However, some applications may continually create tasks that are not released upon completion that will eventually exceed the maximum tasks limit on the server. At that point, no other applications will be able to run. Symptoms: The task count on the net server status screen increases when an application is run but does not decrease back to the initial count when the application exits back to DOS. Note: The first time that each client makes a request of the NetWare Lite server to open a file, a task is created on the server for the DOS shell (COMMAND.COM) on the client. This task will remain open on the server until a client disconnects from the server by typing NET LOGOUT or NET LOGIN to reinitialize the connection. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Windows 3.0 Compatibility DOCUMENT ID#: FYI.P.6044 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Windows 3.0 Compatibility INSTALLATION Follow the regular installation procedures for Windows. Normally Windows will automatically configure itself as if no network is loaded. If you have NetWare Lite loaded when you install Windows, then Windows will set itself up for "Microsoft Network (or 100 percent Compatible)." Putting Windows on a NetWare Lite Network: The following is intended for users who want to install windows in shared mode. Most of this information can be found in the Windows User Guide. The following steps are for the server: 1. Select the Server that you want Windows physically to reside, and create a directory called WIN30. 2. Insert INSTALL DISK 2 and copy the file called EXPAND.EXE to the WIN30 directory. 3. Create a BATCH file in the WIN30 directory called EXPALL.BAT with the following statements: %1 for %%i in (*.*) do %2\expand %%i %2\%%i rename %2\*.sy$ *.sys attrib %2\*.* +r 4. Insert WINDOWS DISK 1 into a floppy drive. Then from the WIN30 directory, run the following: EXPALL <sourcedrive> <destination directory> Example: EXPALL A: C:\WIN30 Note: Step 4 must be repeated for each Windows disk. 5. Enter the NetWare Lite menu utility, by typing NET. Then select "Supervise the network" and then "Network directories." Create a network directory by pressing the <Insert> key. Select the server where your WIN30 directory is located, then enter the path as C:\WIN30. 6. Increase FILES=XX in the CONFIG.SYS file on the server by 20 per client connected. 7. Enter the NET menu utility and select "Supervise the Network" and then select "Server Configuration." Increase CLIENT TASKS=XX by 10 per client connected. Reboot. The following steps are for the client: 1. Load NetWare Lite by typing STARTNET. Map a drive to WIN30: Net Map I: WIN30 <Enter> 2. Change to the I: drive I: <Enter> 3. Type SETUP/N, then follow the Windows installation instructions. Note: At the configuration screen, select the Network option "Microsoft Network (or 100% Compatible)." 4. Reboot the machine. When you reboot the machine, DOS will give you the following message: ┌───────────────────────────────────┐ │Search path contains invalid drive.│ └───────────────────────────────────┘ This message will occur any time you run a program and DOS searches your path. It does this because Windows inserted the I: drive into your path when it was installed. When the machine is first booted, the I: drive has not been mapped yet, so NetWare Lite is unable to locate it. Just ignore the message. When you map the I: drive to WIN30, the message will go away. If you want it to disappear, insert the following line into your AUTOEXEC.BAT file before the path statement: C:\<DOS directory>\SUBST I: C: This line will make the I: drive temporarily search the C: drive, thereby making it a valid statement in the path. As soon as your map command executes, the I: drive will be redirected to a network directory. After you reboot, load the network by typing STARTNET. After you have you have performed your drive mappings and printer captures, you can type WIN to enter Windows. TIPS FOR RUNNING WINDOWS 3.0 Network Operations Set up the NetWare Lite environment before running Windows (that is make sure all drives are mapped, printer ports are captured, and network resources are set up). Mapped Drives and Connections Windows will display a message indicating that "drive does not contain any files" if you try to access a drive on a server that has gone down. Any attempt to access that drive will fail. Under regular DOS, this error is trapped and the client saves enough information to restore automatically the connection to that network directory when the downed server returns to the network. Windows prevents regular DOS from trapping this error. To restore connections to your mapped drive, exit Windows and reissue the NET MAP command when the server is back on the network. (See Question 2 in the Questions and Answers section of this document for more information.) Using Windows to Perform Network Operations Changing the network configuration in the Windows SETUP from "NO NETWORK" to "Microsoft Network (100% Compatible)" on a stand alone machine provides the ability to connect and disconnect network drives and printers through Windows. However, such operations are not supported by Novell. Unpredictable problems may occur. Use "Microsoft Network (or 100% Compatible)" with caution, and if problems occur, change to "NO NETWORK." Selecting Printers If Windows is set up for "NO NETWORK," then Windows does not know how to handle redirections (such as printer captures and drive mappings). Consequently, the user should configure the printer in Windows for either the LPT1.OS2 or the LPT2.OS2 port depending on what has been captured before entering Windows. (Please see Question 3 in the Question and Answers section of this document for more information.) Browse The browse function does not work when trying to attach to servers or trying to capture printers. NetWare Lite Messages Messages sent to network users through NetWare Lite will not be received if the user to whom you are sending the message is in Windows. Windows Modes If you are experiencing a problem that only occurs when NetWare Lite is loaded and if the problem seems unsolvable, experiment with various Windows modes to see if the problem is corrected. The Windows mode can be changed by using one of the following command line parameters: Standard Mode: WIN /s Real Mode: WIN /r Enhanced Mode: WIN /3 HIMEM.SYS If you are using MS-DOS 5.0, make sure that you are using the HIMEM.SYS version (04-09-91) that came with MS-DOS 5.0 and not the one that came with Windows. Windows 3.0 shipped with a more recent driver that has proven to be less compatible with MS-DOS 5.0 than the HIMEM.SYS that DOS is shipped with. Interrupts VPICDA.386 is a patch written by Microsoft that fixes problems that arise when network boards are set to a number greater than 10. It must also be used if you are using interrupt 2. (Which means VPICDA.386 does not need to be loaded if you are using any of the interrupts from 3 to 8.) Use the following instructions to install VPICDA.386: 1. Dowload WINUP4.ZIP from CompuServe (See Fax Document 263 or FYI.P.6087 for information on how to access CompuServe). 2. Unzip the WINUP4.ZIP and copy VPICDA.386 into your Windows\System directory. 3. Edit SYSTEM.INI file. (Use Notepad or another editor.) 4. Remove the "device=*vpicd" line. 5. Replace it with the "device=VPICDA.386" line. Base I/O Addresses I/O addresses below 300 should not be used for network boards on machines that also use Windows. Changes to SYSTEM.INI Make sure that the following line is in the Windows SYSTEM.INI file: [386Enh] UniqueDOSPSP = TRUE Doing this will solve occasional problems with applications that hang a Windows client. Speed Issues with NetWare Lite and Windows See the fax documents concerning the patches that have been released by Novell that increase printing speed. If your network seems slow, these patches could solve your problem. NetWare Lite and Windows: Common Question and Answers. Question 1: Why does my system receive Sharing Violations or lockups when running Windows or Windows' applications? Answer 1: You possibly neglected to set all applications (.EXE, .COM, and .OVL files) to read-only using the ATTRIB command. This can be done by executing the following commands in all directories that might be used across the network: attrib +r *.exe attrib +r *.com attrib +r *.ovl Question 2: What happens if my system loses connections while in Windows? Answer: 2 If a client loses connections temporarily with a server while in DOS, then one of two things will happen: 1. The connection will be reestablished by NetWare Lite. 2. The user will try to perform something that requires a connection and will get an A)bort, R)etry, F)ail error. If the user presses <F> or <R>, then the connection will be reestablished. Unfortunately, Windows will not recognize this "critical error message" and so will not reestablish connections when attempting to perform a network operation such as printing to a network printer. The user must exit out to DOS, perform a function that will reestablish connections after the server is back up (such as DIR on a network directory), then enter Windows again. Question 3: Why do I have to select LPT1.OS2 when I want to print from Windows in a "NO NETWORK" mode? Answer: 3 NetWare Lite is a peer-to-peer network, which means it runs on top of DOS. When a printer is captured, NetWare Lite tricks DOS into printing to another location (such as a printer on another machine). This is why you can print from an application to an LPT1 port, and the job will end up at another machine's printer. Some applications (like Windows) bypass DOS and print directly to the LPT port. So, if you print from an application in Windows, it will bypass DOS, which means it will bypass your capture command and will try to print to a printer on your client (instead of where you want it to go). However, you can trick Windows by going into the WIN.INI file and inserting the following line under the [Ports] section: [Ports] LPT1.XXX= (The suffix can be any three letters.) For example: LPT1.OS2= Windows now interprets that a file called LPT1.OS2 is on your disk; and if you select LPT1.OS2 in "printer setup" under Control Panel, Windows will try to print to this "file." When Windows sends a print job to the file "LPT1.OS2" to DOS, DOS strips off the suffix (OS2, XXX, or whatever) and sends the job to the redirected printer. Question 4: Why can't I print using WordPerfect for Windows? Answer: 4 If WordPerfect printer drivers are being used instead of Windows', the user needs to make some adjustments to make WordPerfect work correctly. The adjustments are similar to the ones made above to Windows. First, go into "select printer." Instead of selecting LPT1 or LPT2, select file. Then enter the name of a file that starts with LPT1 or LPT2: LPT1.XXX For example: LPT1.OS2 This will cause WordPerfect to print to LPT1 correctly for the same reasons it enables Windows to work correctly. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Hardware Trouble Shooting Guide DOCUMENT ID#: FYI.P.6094 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6048 SYMPTOM NA ISSUE/PROBLEM Hardware Trouble Shooting Guide Quite often, apparent problems with NetWare Lite can be traced to the network hardware or the drivers that have been installed. This document describes how to detect some of these problems. The following is an explanation on how to determine whether your network connections are solid. If you are already familiar with this procedure, skip to the next section. How to Run "Verify Network Connections" 1. Insert the original installation diskette (PROGRAM diskette) into the disk drive of one of your machines. 2. Type INSTALL. 3. Select "Verify network connections." 4. Type in the name for the machine. 5. Check to see if the connection appears on your screen, accompanied by the workstation address. 6. Repeat the procedure for all machines on your network. 7. Each time you bring up a new workstation, that workstation's name and node address should show on the following screens: A. Its own screen B. All other screens running "Verify network connections" 8. Remember, "Verify network connections" must be running on all machines on the network concurrently. 9. If one or more of the workstations on your network does not show up on every screen, you have a bad connection somewhere. 10. Allow "Verify network connections" to run for about five minutes to verify that the connections remain solid--in other words, check to see if any workstations blink on and off. If they do, then you have an intermittent connection problem. 11. Finally, ensure that none of your connections are using the same node address (especially when you are using ARCnet boards). Procedure for "Verify network connections" Failures Note: Run Verify Connections between each of these steps to determine if the problem has been solved. 1. The first step is to determine which of the various programs is causing the connection problem. Reboot the machine without loading the network. Type out or print the STARTNET.BAT file to find out what your board driver's name is and replace the NE2000 driver in the example below with your board's driver. Then load the drivers in the following order to determine if each driver loads or if it gives an error message. (Do not forget to replace the NE2000 driver with your board driver.) LSL NE2000 IPXODI A SHARE SERVER CLIENT 2. If any beeps occur when running these programs, you know you have a problem. If any error message occurs, write down the exact message. 3. If you are using a DOS ODI driver, contact the board manufacturer to verify that it is up-to-date. 4. Next, type out the NET.CFG file that is located in the \NWLITE directory to ensure that the interrupt line (IRQ), PORT (I/O), and MEM (Memory Address) entries are the same as the ones that are physically selected on the network board. If they are not, change the settings on your board or the entries in the NET.CFG so that they match. 5. To edit the NET.CFG file, do the following: a. From the \NWLITE directory, use an ASCII editor (DR DOS 6.0's EDITOR for example) to bring up the NET.CFG file. If the file does not exist, then create one according to the following instructions. This example is based on interrupt line 3 and BASE I/O Address 300 settings: #Setup the NE2000 board LINK DRIVER NE2000 INT 3 MEM D0000 (NOTE: NE2000 does not use this line.) PORT 300 Notes: a. INT, MEM, and PORT need to be exactly one TAB away from the left margin. b. Not all boards use shared memory, so your NET.CFG may not contain a MEM setting. c. Any line starting with a # sign is a comment line. 6. Try changing interrupt line (IRQ), PORT (I/O), and/or MEM (Memory Address) settings on the network board to ensure that there are no other hardware conflicts. Then reinstall NetWare Lite or edit the NET.CFG file so that NetWare Lite recognizes the new board settings. The NetWare Lite v1.1, the README.TXT document in Section 2: INSTALLING NetWare LITE AND LOGGING IN, and Fax Document 212 or FYI.P.6054 contain more information on resolving I/O and IRQ conflicts. 7. Strip down the AUTOEXEC.BAT and CONFIG.SYS files. Afterwards your files should look similar to the following examples: AUTOEXEC.BAT CONFIG.SYS @ECHO OFF FILES=30 PROMPT $p$g BUFFERS=30 C:\DOS;C:\NWLITE LASTDRIVE=M 8. If this solves the problem, add your original command lines back into the AUTOEXEC.BAT and CONFIG.SYS files one at a time starting with the CONFIG.SYS file, rebooting the machine, and running verify connections between each one until you find the command line causing the problem. 9. If your network board uses a Shared Memory Address (MEM), use a memory manager (such as DR DOS 6.0's EMM386.SYS) to exclude the range of memory that the board uses. This will prevent another program from using that memory address (Please refer to Fax Document 264 or FYI.P.6076 for information about DR DOS 6.0 and MS-DOS 5.0 memory managers). 10. Remove any possible conflicting boards (such as modem, mouse, bus boards). Afterwards, your machine should only contain the network board, a drive controller board, and a video board. If the problem goes away, put the boards back in one at a time to see which board was causing the problem. 11. Try putting the network board in a different slot on the motherboard. 12. Check or change cables, T-connectors, and terminators. Remove anything that might be causing interference on the network cable (such as speakers or florescent lights). If you are using an ARCnet topology, check for a bad hub or a bad port on the hub. If you are using a Twisted-Pair topology, check for a bad concentrator or a bad port on your concentrator. 13. Try slowing down the bus speed on your machines. The bus speed should never be faster than 8 MHz. Note: Realize that bus speed and clock speed is not the same thing. Your bus speed can usually be slowed down through the CMOS setup. In some instances, however, the only way to slow down the bus speed is to slow down the clock speed (if your machine has a turbo switch, turn the turbo off). Refer to your user's manual for more details. 14. Try a different network board. The recommended network boards are listed on the back of the NetWare Lite box and the approved ODI driver for each recommended board is included on the NetWare Lite Driver diskette. 15. Scan for viruses. You can obtain software to perform this scan by calling the McAfee BBS at 408-988-4004 or dial 408-988-3832 for voice. You may also contact your local dealer for virus protection software. 16. Try using a different PC to reveal any possible conflicts between your machine and the network board. 17. Run CHKDSK /F or a third-party disk utility on each hard drive to recover any lost clusters and to fix any other problems. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: EVOLUTION/2 Compatabilitity DOCUMENT ID#: FYI.P.6045 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM MAS 90 EVOLUTION/2 Compatibility The following is a technical bulletin, reproduced with permission from State of the Art, Inc. It discusses NetWare Lite's compatibility with MAS 90 EVOLUTION/2. MAS 90 EVOLUTION/2 Technical Bulletin Bulletin No.: 91008 Date: Novem ber 22, 1991 Application: Library Master Level: 1.2x Subject: NetWare Lite Compatibility Issues State of the Art, Inc. has evaluated the Novell NetWare Lite Network Operating System and found it to be fully compatible with MAS 90 EVOLUTION/2. NetWare Lite is a low-cost, peer-to-peer network solution that does not require a dedicated file server and offers compatibility to most NETBIOS networking adapters. The evaluation performed by State of the Art, Inc., consisted of an 80386 nondedicated file server, 80386 workstation, MS-DOS Level 3.30 and MS-DOS Level 5.0, and Western Digital Ethernet network boards. We also configured NetWare Lite using ARCnet network boards. Both methods of connecting workstations were found to be compatible with MAS 90 EVOLUTION/2 products. Because of the inherently slower nature of a peer-to-peer topology, it is recommended that 80386- or 80486-based systems be used for both file servers and workstations. To use NetWare Lite as a network environment with your MAS 90 EVOLUTION/2 installation, a Network version of the Library Master is required. The Network Library Master must be Level 1.2x or above and should be installed on the designated file server of the NetWare Lite Network using the network installation procedure described in Section 7 of the Library Master documentation. It appears that MAS 90 EVOLUTION/2, used in conjunction with NetWare Lite version 1.0, is incompatible with DOS partitions that are larger than 32 MB. System freezes and intermittent lockups may occur when drive partitions larger than 32 MB in DOS 4.0x, or other methods of increasing drive sizes, are used. If these conditions persist, shrink your DOS 4.0x partitions to less than 32 MB or reformat your hard drives with DOS 3.30 or DOS 5.0. Both methods have been found to eliminate the problem. Because of the size of the NetWare Lite shell, the amount of memory available to the MAS 90 EVOLUTION/2 software may not be sufficient for some applications under MS-DOS 3.3x. Under MS-DOS 5.0 this issue can be addressed by loading various network drivers into high memory, gaining approximately 40 KB of additional RAM. However, even when using MS-DOS 5.0 with NetWare Lite, you may experience memory limitations because the remaining available memory can be limited by DOS configuration issues. Because it is impossible to predict the actual amount of available RAM you may have on your system at any one time, we suggest that you establish a minimum of 530 KB to 550 KB of available RAM before entering the MAS 90 EVOLUTION/2 software. This amount of available RAM should be sufficient to run the software in a multi-user mode under most circumstances for all applications. In order to ensure that the MAS 90 EVOLUTION/2 software functions properly in the NetWare Lite environment, you must check the following minimum configuration issues. To configure your system for NetWare Lite: 1. The file-server disk drive and each workstation should be configured and operational before installing MAS 90 EVOLUTION/2. You should configure and test printers and have supervisor access rights before application installation. 2. The CONFIG.SYS file for file servers and workstations must contain the following commands: FILES=50 BUFFERS=32 LASTDRIVE=M 3. The AUTOEXEC.BAT file for the file server with MAS 90 EVOLUTION/2 installed must contain the following commands: SET BBTERM=TO Sets the file server identifier to TO. SHARE/F:4096/L:500 Invokes SHARE with file buffers set to 4096, number of file locks set to 500. 4. The AUTOEXEC.BAT file for each workstation must contain the following commands: SET BBTERM=T1 Sets the workstation identifier to T1. Each workstation must have a unique identifier (e.g., T1..T9, T10, T11, TA, TB, etc.). SHARE/F:4096/L:500 Invokes SHARE with file buffers set to 4096, number of file locks set to 500. 5. Make sure that each workstation and the file server are all running with the same version of DOS. This is necessary because the SHARE command is used for File and Record locking, and consistent implementations of SHARE are a requirement for NetWare Lite to function properly. 6. The drive letter for the server should be higher than the highest drive letter for any workstation. For example, if each local workstation has a C and D drive, the server should be designated as an E drive, relative to the workstations. Otherwise, data corruption may occur. IMPORTANT While NetWare Lite is designed as a peer-to-peer drive-sharing network, the MAS 90 EVOLUTION/2 programs and data files require a server and workstation configuration. All programs must be loaded onto the same server drive and in the same directory. All data files are accessed through Library Master programs and their location as known to MAS 90 EVOLUTION/2 is relative to the drive where Library Master was installed. It is recommended that all data files be located in the same directory where the application programs were installed. However, if you choose to distribute data files among other drives on the network, do not assign each workstation a different drive designator for the server drive. Each workstation must access the server drive using a similar drive letter, or MAS EVOLUTION/2 may not be able to access those data files. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing Paradox 3.5 DOCUMENT ID#: FYI.P.6047 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Installing Paradox 3.5 Before Beginning To install Paradox 3.5 on a NetWare Lite network, you must perform the steps described below. Please read this entire document before beginning the installation. By doing so you will get a better understanding of the process. You may also discover that some of the steps have already been done and do not need to be repeated. However, if you run into problems, try starting from the beginning and redoing all the steps. The installation is divided into three parts. The first part is the preparation of the server. The second part is the installation/configuration of Paradox. The third part is setting up the users. Any text that is shown between quotations (" ") is an example of what you would enter on the keyboard to perform the step being described. The text can be entered either uppercase or lowercase. Do not type the quotations. Prepare the Server Please refer to the NetWare Lite manual, README.TXT file, or other fax documents if you need more information to complete any of the following steps. 1. Install NetWare Lite on the machine that will be the file server. 1a. Select "Make this machine a client and a server" option. 1b. After NetWare Lite is installed, reboot the machine and load the network by typing "startnet" at the DOS prompt. 1c. Be sure to run SHARE.EXE whenever the network is loaded. 1d. Test the network to make sure it is functioning properly. 1e. As a minimum, you should use the "Verify network connections" option in the NetWare Lite installation program. 2. Increase files handles and client tasks. The number of file handles is determined by the FILES= command in the CONFIG.SYS file. Use the NET utility to increase the client tasks for the server. This is done by selecting "Supervise the network," then "Server configuration," then "Client tasks." These modifications will take effect the next time the server is booted. 3. Create directories on the server's local drive where Paradox will be installed. You will need to create separate directories for the Paradox program files and the Paradox network control file. Also create a users' directory where each user's "home" directory will be located. As an example, execute the following commands at the DOS prompt (if the c:\apps directory already exists): "md c:\apps\pdox35" "md c:\apps\pdox35\pdoxdata" "md c:\users" These directory names will be referred to throughout this document; however, these names are only examples. If you want to use different directory names, simply substitute them for the names that have been used. You may also use different drive letters than the ones used if you prefer. However, if you run into problems, try using the names and letters used in this document. 4. Create separate network directories for the Paradox program files and network control file. The procedure for completing this step is as follows: 4a. Make sure the network is running and log in as supervisor (or any other account with supervisor privileges). 4b. Type "net" at the DOS prompt to start the NET utility. 4c. Highlight "Supervise the network" using the arrow keys, and press the <Enter> key. 4d. Highlight "Network directories," and press the <Enter> key. 4e. Press the <Insert> key to add a new network directory. 4f. Highlight the name of the server where Paradox will be installed, and press the <Enter> key. 4g. Enter a name for the network directory where the Paradox program files will be located, such as "pdox35." 4h. Enter the complete path where the Paradox program files reside on the server. In the example, this would be entered as "c:\apps\pdox35." 4i. Leave the "Default access rights" as "ALL." Press the <Esc> key, then press the <Enter> key to save the new network directory definition. 4j. Repeat steps 4e through 4i to define a second network directory for the Paradox network control file. Use "pdoxdata" for the network directory name and "c:\apps\pdox35\pdoxdata" for the path. 4k. Repeat steps 4e through 4i to define a network directory to be used as the users' directory. Use "users" for the network directory name and "c:\users" for the path. 4l. Press <Alt>+<F10> to exit the NET utility. Install Paradox If Paradox is already installed, skip to the next paragraph; otherwise, install Paradox on the server's local drive according to the documentation supplied with Paradox. You will be installing Paradox as a network application but not to a network directory. When prompted for drive letters and paths, use the appropriate local drive letters and paths as though you were installing Paradox as a stand-alone application. During the installation, you will be prompted for information specific to your setup, such as the network type you are using. Consult the Paradox documentation if you require additional information about how to respond to specific questions. Answers to critical questions are shown below. Network type 6 (Other) Network control file: c:\apps\pdox35\pdoxdata Set Up the Users Paradox allows each user to have a custom configuration for their Paradox session. To use this feature, you must create a separate directory for each user who will use a custom configuration. Create a user directory for each user by entering the following command at the DOS prompt: "md c:\users\username" Substitute "username" with each person's name. The example shows you how to set up user directories on the server. User directories can be set up on the workstations; however, this must be done from each workstation. Next, prepare to update the paradox network-control file, and change the attributes of the Paradox executable files to "read-only" by entering the following commands at the DOS prompt: "subst h: c:\apps\pdox35" "subst i: c:\apps\pdox35\pdoxdata" "h:" "attrib +r *.exe" "nupdate" If you get a "command or filename not found" message while trying to execute the SUBST or ATTRIB command, make sure that the directory where they reside is in your current path. You must also run the Paradox Custom Configuration Program (CCP) to create a PARADOX.CFG for each user. Whether you make user directories on the server or on each workstation, the directories must exist before starting the CCP. See Chapter 14 of the Paradox Users Guide if you require more information on how to use the CCP. The basic steps are outlined below: 1. Start the CCP by entering the following command at the DOS prompt: "paradox custom" 2. When in the CCP, select "Net|SetPrivate" from the main menu. 3. Enter the path to the user's directory, such as: "c:\users\<username>" The directory you specify must exist before starting the CCP. 4. Press <F2> to save the configuration. Choose "Network" when the system prompts you for a location to save the PARADOX.CFG file. 5. Repeat steps 1 through 4 for each user. Starting Paradox from a Workstation The easiest way for a user to start Paradox is to create a batch file that includes the following commands: "net map h: pdox35" "net map i: pdoxdata" "net map j: users\%1" "set t=%path%" "path h:\;%path%" "j:" "paradox -share" "path %t%" After the network software has been loaded at the workstation and the user has logged in, the batch file should be executed. If the batch file was called PDOX.BAT, the user would type "pdox <username>" at the DOS prompt, substituting the name of the user directory for <username>. <username> gets substituted for "%1" in the batch file. Starting Paradox on the Server To start Paradox on the server, create a batch file as instructed in "Starting Paradox from a Workstation" paragraph. Modify the batch file as follows: "subst h: c:\apps\pdox35" "subst i: c:\apps\pdox35\pdoxdata" "cd c:\users\%1" "set t=%path%" "path h:\;%path%" "paradox -share" "path %t%" "subst h: /d" "subst i: /d" This batch file can be run on the server whether the network software has been loaded. If the batch file were named PDOX.BAT, the user would enter "pdox <username>" at the DOS prompt, substituting the name of the user directory for <username>. <username> gets substituted for "%1" in the batch file. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Network Setup DOCUMENT ID#: FYI.P.6050 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Network Setup Introduction NetWare Lite is a peer-to-peer network that enables users to share printers and disk drives. To have a better understanding of NetWare Lite itself, many users need to learn some new network concepts and terminology. This document is designed to help make this learning process easier. Loading the Network NetWare Lite is a DOS based network. In other words, it relies on DOS to communicate with your computer hardware and software (as opposed to NetWare 2.x and 3.x that do not use DOS to perform these functions). NetWare Lite is made up of several terminate-and-stay resident programs (TSRs) that load themselves into memory. These programs can be divided into two general categories--those that deal with the network board and those that make up NetWare Lite. Network Boards LSL <DOS ODI Driver> (Example: TRXNET.COM) IPXODI A NetWare Lite SHARE (DOS Program) SERVER CLIENT These programs are normally executed from a batch file called STARTNET.BAT. STARTNET.BAT When NetWare Lite is installed, a file called STARTNET.BAT is created. STARTNET.BAT loads the network software into memory by running certain programs one at a time. If a machine is setup to be both a server and a client, STARTNET.BAT will look like the following: LSL <DOS ODI Driver> (Example: NE2000) IPXODI A SHARE SERVER CLIENT Note: All of these files, with the exception of SERVER.EXE, can be loaded into upper memory. These files can be run from a batch file or from the command line. Some people even add these commands into their AUTOEXEC.BAT. This will work; however, Novell recommends that you use a separate batch file (such as STARTNET.BAT) to run these programs. When the network programs are loaded from a separate batch file, problems are easier to troubleshoot. STARTNET can be called from your AUTOEXEC.BAT by inserting the following command into your AUTOEXEC.BAT file (usually near or at the end): call startnet LSL, the DOS ODI driver, and IPXODI are programs that enable the computer to interface with the network board. Note: When you load IPXODI, you will do so with an A parameter (IPXODI A). This parameter causes the program to load itself without some of the overhead that is unnecessary for NetWare Lite to run thus saving memory. SHARE.EXE is a program that enables file sharing. Consequently, it must be loaded on servers (because they are likely to have files that other clients are trying to access concurrently). SERVER.EXE must be loaded on each machine that has network resources (such as printers and disk drives) that need to be shared with other clients. CLIENT.EXE must be loaded on each machine that will need to access network resources. Example If a user wants to use computer 1 to print to a printer on computer 2, then computer 1 must have CLIENT.EXE loaded; and computer 2 must have SERVER.EXE loaded. Likewise, if a user at computer 1 wants to access station 2's hard disk, then computer 1 must have CLIENT.EXE loaded; and computer 2 must have SERVER.EXE loaded. If a computer needs to have access to its own printer and SERVER.EXE has been loaded, then the computer will need to load CLIENT and capture a port because the printer has become a network printer. Users and Logging In The supervisor can log in to the network by typing: NET LOGIN SUPERVISOR NetWare Lite allows network administrators to place limits on network access through passwords and directory access rights. The supervisor must create users so that individuals will be recognized by the network--then those users will be able to log in when they need network access. Users can be added to the network by doing the following procedure: 1. Load the network (as explained above). 2. Type NET LOGIN SUPERVISOR 3. If requested, enter a password. 4. Type NET 5. Select "Supervise the Network." 6. Select "Users." 7. Press <Insert>. 8. Enter <username>. 9. Enter any information in about the user. For example, you can issue the user a password or give him supervisor privileges. Now, a user can log in when desired from any machine. Network Resources Network resources are peripherals--usually printers, disk drives, and CD-ROMs--that are made available to all users on the network. Local printers become network printers, and disk drives and CD-ROMs become network directories. Novell suggest network directories and printers be given descriptive names. Good names for network directories might be BORLANDC, WORDPERFECT, GAMES, GIFS, or PUBLIC. Good names for network printers might be LASERJET-II, EPSON-DOT, or APPLE-LAS. Names that might not be good are CDRIVE, PRINTER1, and PRINTER2. These names provide no indication of what applications or what kinds of printers are being made available. Notice that during installation, NetWare Lite creates a CDRIVE network directory for you. When you become familiar with the product, this resource ought to be given a more descriptive name. Network Directories The first type of network resource that a NetWare Lite administrator can create is a network directory. These directories need to be created so that individuals can gain access to other users' hard drives. Network directories also give the network administrator power to regulate network access. Users can only access network directories that the network administrator gives them access to. Create a network directory by doing the following steps: 1. Load the network (as explained above). 2. Type NET LOGIN SUPERVISOR 3. Enter a password if requested. 4. Type NET 5. Select "Supervise the Network." 6. Select "Network Directories." 7. Press <Insert>. 8. Select the server where the actual directory resides. 9. Type <directory name> (example: WP). 10. Type in the actual directory path (example: C:\WP51). Assign rights by doing the following: 1. In the same Network Directories screen, you can change "default access rights" and "users with nondefault rights." Refer to the NetWare Lite manual for instructions on how to do this. A user cannot access another user's machine unless he maps a drive letter to a network directory that has been set up. The following section explains mapping: Mapping Each computer recognizes a certain number of disk drives. Normally, a machine will have two floppy drives (A: and B:) and one hard drive (C:). NetWare Lite communicates to DOS and your machine that there are more drives on your machine than these three. Mapping a drive letter takes unused DOS drive letters and assigns them to network directories so that users are able to access the directories. This can be done both through the NET utility (by typing NET) and through the NET MAP command. To map a drive letter using the NET utility, do the following: 1) Type NET at the command line. 2) Select "Map drive letters." 3) Select the drive letter you wish to map (such as G:). 4) Select the network directory to which you wish to map. To map a drive letter to a network directory from the command line, enter the following: NET MAP <drive letter> <network directory> Example: After setting up a WORDPERFECT network directory, a user might enter the following command: NET MAP G: WORDPERFECT If the network directory WORDPERFECT is physically located on server 1 in C:\WP51, then whenever the user goes to G: (assuming G: has been mapped to WORDPERFECT), he will see the contents of C:\WP51 on server 3. The user will not be able to access any other directories (other than subdirectories underneath C:\WP51) using G:. If server 1 has the following directory structure and a user has mapped G: to C:\WP51, then that user will be able to access both the \USERS and the \DATA subdirectories. However, he will not be able to access the \BORLANDC directory. C:\WP51 |-------\USERS |-------\DATA \BORLANDC Lastdrive The LASTDRIVE= command in your CONFIG.SYS reserves extra DOS drive letters for NetWare Lite's use. For example, if you included the statement "LASTDRIVE=M" in your CONFIG.SYS and you had the above configuration (A:, B: and C:), then you would have ten drive letters available for mapping (D: through M:). Network Printers The setup process is similar for network printers. Network printers can be created by doing the following steps: 1. Load the network (as explained above). 2. Type NET LOGIN SUPERVISOR 3. Enter a password if requested. 4. Type NET 5. Select "Supervise the network." 6. Select "Network printers." 7. Press <Insert>. 8. Select the server where the printer is actually connected. 9. Type <printer name>. 10. Select one of the "Available server ports." Make sure your printer is attached to the port that you select. 11. Press <Esc> to use the default settings (such as setup strings or CPS), or change as desired. Capturing Now, to print to this printer, the user only needs to capture one of the personal ports to the network printer. The user could do this by issuing the following command: NET CAPTURE LPTX <network printer> Example: NET CAPTURE LPT1 LASER-JET Ports LPT1, LPT2, and LPT3 can be used to capture while any port (parallel or serial) can be used to physically attach a printer. Note: There is a difference between a "captured" port and the port to which a printer is attached. A printer can be physically attached to any port (parallel or serial). This port is entered when a network printer is created so that NetWare Lite interprets where to send print jobs that are directed to that printer. After those printers are established, ports LPT1, LPT2, and LPT3 are freed so that they can be used to capture network printers. That means that a user could have a printer physically attached to LPT1 and could capture LPT2 to that printer. He could then capture LPT1 to a printer located on someone else's machine if desired. Example Network Setup The following is a comprehensive example that will take the reader through the setup of an imaginary network. This example will involve three machines: KENDALL-386, DAVE-286, and JOEL-486. KENDALL-386 is set up as a client only. DAVE-286 is set up as server only, and JOEL-486 is set up as a client/server. Because DAVE-286 is a server only, it will be unable use any network resources. Likewise, KENDALL-386, because it is set up as a client only, will not be able to allow others to use its drives or printers. Verify Network Connections "Verify network connections" should be run once after you have initially set up the network to ensure that you do not have any hardware or driver problems. It should also be run any time you think you might have a connection problem. See Fax Document 215 or FYI.P.6094 for more details. Follow this procedure to "Verify network connections": 1. Load the network (as explained above). 2. Insert PROGRAM DISKETTE into a disk drive. 3. Type INSTALL 4. Select "Verify network connections." 5. Enter the name of each machine. 6. "Verify network connections" should be running on all machines. 7. Each screen should look something like the following (all machines that are running "Verify network connections" should show up): Name Address JOEL-486 00001B1E6082 KENDALL-386 00002C3I4983 DAVE-286 00008B9N4440 Let "Verify network connections" run for about five minutes to make sure that none of the machines disappear or flicker on and off. If "Verify network connections" fails, then you know that you either have a hardware problem or a driver problem. Please refer to Fax Document 215 or FYI.P.6094 for possible solutions. User Setup Next, log in to the network to setup users. Follow the instructions above for setting up users. In the example, seven users have been set up: Joel Kendall Dave Rebecca Kevin Steve Chad Joel, Kendall, and Dave were given supervisor privileges, which means that they can perform the same functions as the supervisor. Remote Management If a server allows "Remote management," then users can change the server configuration from remote stations (clients). KENDALL-386 and JOEL-486 were set up so that they could not be remotely managed. DAVE-286 was set up so that it could be remotely managed by issuing the following commands: 1. Type NET at the DOS prompt. 2. Select "Supervise the network." 3. Select "Server configuration." 4. Select <server name>. 5. Arrow down to "Allow remote management," and select "Yes" or "No." 6. The change will take effect when the server has been rebooted. Setting up Network Resources Next, set up network printers and network directories. JOEL-486 has a printer attached to COM1. It is a HP Laserjet III called HPIII. DAVE-286 has a dot matrix printer attached to its LPT1 port called OKIDATA. Any time someone on the network wants to print to one of these printers, they need to capture a port. Remove all the CDRIVE directories that NetWare Lite created, and create the following four network directories: WP51 DBASE COMMON DATA WP51 is physically located on JOEL-486. Because JOEL-486 is set up as a server/client, the user who is using JOEL-486 can use the machine even though other user might be accessing WordPerfect from this machine. DBASE is physically located on DAVE-286. Because DAVE-286 is set up as a server only, employees using DAVE-286 cannot access network resources; although, they will still be able to access their local drives (but not local printers). COMMON and DATA are both located on DAVE-286. KENDALL-386 cannot contain network directories because it is set up as a client only. Sample Files The following is an example of the files used to fine tune NetWare Lite followed by a list of configuration tips for each file: CONFIG.SYS AUTOEXEC.BAT STARTNET.BAT LOG.BAT <NAME.BAT> NET.CFG CONFIG.SYS The server keeps track of all files that are open. As more workstations (clients) attempt to access a server, more files will be opened. The number of files that can be opened needs to be increased on any server that will be allowing clients to access files. Enter the following command somewhere in the CONFIG.SYS, or increase it if it is already there: FILES=XX AUTOEXEC.BAT At the end of AUTOEXEC.BAT, the following command has been included so that the network will automatically be loaded when the computer is booted: call STARTNET STARTNET.BAT The STARTNET.BAT file will be different on each machine depending on its configuration. The following is an example of the one machine set up. All lines that do not have a specific designation are included in all three versions of STARTNET.BAT. Other lines are only included in the STARTNET.BAT files for the designated machines: lsl ne2000 ipxodi a share (on DAVE-286 and JOEL-486) See Fax Document 111 or FYI.P.6003 on configuring SHARE.EXE. server (on DAVE-286 and JOEL-486) client (on KENDALL-386 and JOEL-486) <NAME>.BAT Create a batch file for each user that logs each user into the network. (For example: Rebecca logs in using a batch file called BEC.BAT.) An individual batch file might contain the following commands: net login rebecca net map d: wp51 net map e: dbase net map f: common net map g: data net capture lpt1 HPIII net capture lpt2 OKIDATA Make a directory on each machine where all of these batch files exist called \NETBATCH and include this directory in the path of each machine. Now, whenever Rebecca wants to log in to the network, she can go to any machine that has client loaded and type BEC, and she will be logged into the network. Remember, this only works because the BEC.BAT batch file was copied over to the \NETBATCH directory of each machine. NET.CFG This file was created by NetWare Lite at installation. It contains information specific to the network board on each machine. See Fax Document 215 or FYI.P.6094 for more information on this file. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite and Third-Party Caches DOCUMENT ID#: FYI.P.6111 DATE: 01DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: FYI.P.6009 SYMPTOM NA ISSUE/PROBLEM NetWare Lite and Third-Party Caches NetWare Lite v1.1 now ships with a disk cache called NLCACHE. See Fax Document 155 or FYI.P.6075 for particular in-depth details. ***** WARNING ***** Caches other than the NetWare Lite Cache may need to have delayed writes, deferred writes, posted writes, or queued writes disabled if they are used with NetWare Lite. Many cache programs "wake up" to do writes in the background, and they do not protect themselves from reentry with a DOS-critical section callout. If you use a cache (other than the NetWare Lite Cache) with deferred writes, posted writes, or queued writes turned on, you may get random hangs, data corruption, or other abnormal behavior. To use a cache other then the NetWare Lite Cache, call the cache company's technical support group to find out if their cache's deferred writes, posted writes, or queued writes work with NetWare Lite. Many caches do not allow delayed writes, deferred writes, posted writes, or queued writes when using a peer-to-peer network. However, the NetWare Lite Cache can use delayed writes. If you are using a cache that has one of the above options, make sure the option is turned off. Some cache tuning may be necessary for best results. Note: Do not load two cache utilities on the same machine. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: The IPXODI Driver DOCUMENT ID#: FYI.P.6006 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM The IPXODI Driver The IPX shipped with NetWare Lite (IPXODI) is not new and is not special to NetWare Lite. Novell has made a general decision to convert from "linked" IPX to IPXODI. IPXODI is shipped with the LAN Workplace for DOS product and with the DOS/Windows shell kit. Novell will convert from linked IPX to IPXODI for red-box NetWare soon. IPXODI is functionally identical to the linked version of IPX, although the Link Support Layer (LSL) offers multiple-protocol and Multiple Link Interface Drivers (MLID) capabilities. NetWare Lite can be run on top of either linked IPX or IPXODI but not on both. STARTNET.BAT, which is created as part of the NetWare Lite installation, should be modified not to load LSL (the ODI driver) and IPXODI if linked IPX is already being loaded elsewhere (similar to the AUTOEXEC.BAT). SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DacEasy Compatibility DOCUMENT ID#: FYI.P.6057 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM DacEasy Compatibility The following steps should be followed when using DacEasy Accounting, Payroll, and Point of Sale Network software. Installing DacEasy for the First Time 1. Install NetWare Lite. Please see Fax Document 235 or FYI.P.6050 for help with installing and configuring NetWare Lite. 2. Map Drive Letters. The next step is to map a drive letter in NetWare Lite by doing the following: a. Type STARTNET b. When the network is loaded, log in by typing NET LOGIN SUPERVISOR c. Type "NET MAP <drive letter> CDRIVE <server name>" Example: NET MAP G: CDRIVE SERVER_1 Note: The CDRIVE network directory is created for you when you install NetWare Lite. d. Now, any user can access this SERVER_1 by going to the G: drive. 3. Install DacEasy. Please see the manufacturer's installation instructions for DacEasy. Make sure that you install from the drive in NetWare Lite where the program will be stored. For example, if you are going to store DacEasy on the G: drive, then your installation command should be the following: G:\>a:install. The program will verify on which drive you are going to install the program. Reinstalling DacEasy for a Network If you have already installed one of the DacEasy programs on a single user machine and you are now connecting the network, you will be required to make a change in the mapping. 1. Change to the drive letter that you have mapped. Example: G: 2. Change to the applicable directory by typing the following command applicable to the DacEasy program being used: Program Command Accounting CD\DEA4\DEA4BAS E Payroll DEP4\DEP4BASE Point of Sale DPOS\POSBASE 3. Delete the applicable file by typing the following command applicable to the DacEasy program being used: Program Command Accounting DEL DEA4CID.DB Payroll DEL DEP4CID.DB Point of Sale DEL DEA4CID.DB 4. Change back to the previous directory by typing CD.. 5. Start the applicable program by typing the following command applicable to the DacEasy program being used: Program Command Accounting DEA4 Payroll DEP4 Point of Sale DPOS 6. When the program sends the prompt "New user or Upgrading from an earlier version," respond with the "New User" option. 7. Follow the prompts as when first installed. Put in an identifier or identification for the companies' books that are located in this subdirectory. 8. Enter the path where your data files exist. Remember to use your new mapped drive. For example, the data path could be: G:\DEA4\DATA Note: Make sure that this directory exists. 9. If the data is located in that subdirectory, the program will prompt the following message: "Do you wish to add it to the company file?" Respond with a "Y" 10. All clients should use the same mapped drive to access the program. Example: If you have mapped G: drive to install DacEasy to the server, then all clients should map G: to the server. Configuration files should be increased in the CONFIG.SYS of the SERVER where DacEasy is located by about 50 per client using DacEasy. SHARE.EXE needs to be loaded when an application is running that requires users to share files on a server. This program is normally run in the STARTNET.BAT file or in the AUTOEXEC.BAT file. The /F and /L parameters may need to be increased to get DacEasy to run across a network. Please see Fax Document 111 or FYI.P.6003 on SHARE for more information on how to increase these parameters. The following parameters can be used as defaults: SHARE /F:8000 /L:400 Increase the client tasks for the server by about 10 per client by issuing the following commands: a. Type NET b. Select "Supervise the network." c. Select "Server configuration." d. Select the server where DacEasy is physically located. e. Increase the "Client tasks" number. If you follow the above steps, you should not have problems running DacEasy. If you do experience problems, please call the DacEasy technical support line at 1 (214) 248-0205 or 1 (900) 370-2322. The charge is $1.50 per minute on your credit card if using the 214 line or on your phone bill if using the 900 line. If you are experiencing network problems, please call the NetWare Lite technical support team at 1 (900) 454-5483. The charge is $2.00 per minute. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Known Documentation Errors DOCUMENT ID#: FYI.P.6001 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Known Documentation Errors Your manual may contain one or more of the following errors: Page 7: In the "Log in to NetWare Lite" section, step 3, "NET LOGIN" should read "NET LOGIN SUPERVISOR." Pages 36 These pages incorrectly state that the supervisor and 60: privileges are not required. Supervisor privileges are required except for a server running on your own machine. Page 106: This page incorrectly states that COM1 and COM2 can be captured using the NET CAPTURE command. Only LPT1, LPT2, and LPT3 can be captured. However, network printers can be assigned to COM ports on servers. Page 107: This page is missing the "notify" capture setting. You can specify the notify option using the "N=Y" or "NOTIFY=Y" option. If set, the server will send you a message when the print job is done. Page 149: The discussion of network configuration files is not needed. The NetWare Lite INSTALL utility generates the correct NET.CFG file from the options you select during installation. After installation, you can edit the NET.CFG file using any standard ASCII text editor. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing WordPerfect 5.x DOCUMENT ID#: FYI.P.6090 DATE: 03JAN92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6050 SYMPTOM NA ISSUE/PROBLEM Installing WordPerfect 5.x This document was created to help you run WordPerfect on a NetWare Lite server. If you want more than one user to have access to the WordPerfect program, you must make the following changes: ***** WARNING ***** If you plan on using WordPerfect on two or more machines, you must obtain a multiple-copy site license from the WordPerfect Corporation. ┌──────────────────────────┬─────────────────────────────────── ─────────┐ │ FASTPATH STEPS │ DETAILED INSTRUCTIONS │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 1. Type CD C:\WP1 │ 1. It is necessary to be in the directory │ │ │ where the WordPerfect files are located.│ │ │ This is usually called c:\wp. To change│ │ │ to this directory type "cd \wp" and │ │ │ press <Enter>. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 2. Type INSTALL │ 2. WordPerfect has an installation │ │ │ procedure that allows you to change the │ │ │ machine's configuration. To access the │ │ │ installation menu, type INSTALL and │ │ │ press <Enter>. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 3. Press <Y> to │ 3. Press <Y> to continue with the │ │ continue. │ installation procedure. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 4. Press <Y> to │ 4. Because you are installing these files │ │ install to hard │ for a NetWare Lite server, press <Y> to │ │ disk │ install to your hard disk drive. │ │ │ │ │ │ Note: You must have a hard drive to │ │ │ install your computer as a server with │ │ │ NetWare Lite. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 5. At the installation │ 5. Select "3" to perform a customized │ │ menu, select "3." │ installation onto a network. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 6. At the Network │ 6. The WP{WP}.ENV file is the file that │ │ Customization │ lets WordPerfect recognize a network │ │ Installation Menu, │ environment and allows the WordPerfect │ │ select "5." │ program files to be shared by multiple │ │ │ users. To check or create this file, │ │ │ select "5." │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 7. Press <Y> to create │ 7. If the WP{WP}.ENV file does not │ │ if necessary. │ already exist, the computer will prompt │ │ │ you to create it. Press <Y> for yes. │ │ │ │ │ │ Note: If this file already exists, │ │ │ the computer will skip this step. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 8. At the Check WP{WP} │ 8. The Check WP{WP}.ENV File menu appears │ │ .ENV File Menu, │ and allows you to select the type of │ │ select "4." │ network environment you will be using. │ │ │ Because NetWare Lite is not listed, │ │ │ select "4" for IBM. Secondary selection│ │ │ if the first does not work is select "0"│ │ │ for other. │ │ │ │ │ │ Note: Do NOT select 1 for Novell │ │ │ NetWare. This will not configure your │ │ │ machine for NetWare Lite. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │ 9. Enter the directory │ 9. At the bottom of the screen, the │ │ and path for setup. │ computer will prompt you for the path │ │ │ you want the setup files to be copied to│ │ │ Normally you would set this path to the │ │ │ same location of the other WordPerfect │ │ │ files. If that is correct, type in that│ │ │ path and press <Enter>. If not, change │ │ │ it to reflect the desired path. │ ├──────────────────────────┼─────────────────────────────────── ─────────┤ │10. Press <F7> to exit │10. Installation is now complete. Press │ │ installation │ the <F7> function key to exit the │ │ │ installation menu. │ └──────────────────────────┴─────────────────────────────────── ─────────┘ From now on, when you start WordPerfect, the program will prompt you to enter a three-letter username. This is to distinguish one user from another. Each user must go into the setup <Shift>+<F1> and define the location of their own files. Each user must specify the drive letter they mapped WordPerfect to in NetWare Lite for the location of the system files. Printing When a station is setup as both a server and client by default, the station is configured so that SERVER.EXE is loaded before CLIENT.EXE. SERVER.EXE may be loaded after CLIENT.EXE. However, upon loading the server, a warning message will appear indicating that printing may not function correctly. To eliminate this warning, simply verify that server is loaded before client. When a printer is selected in WordPerfect, an option is available for specifying whether the printer is on a network or local. WordPerfect assumes that printers are local unless otherwise specified. It is fine to select WordPerfect's default and specify the printer as local. If you choose to make the printer a network printer, be sure to suppress the top of form on the last page of the document. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Supported Network Boards DOCUMENT ID#: FYI.P.6089 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Supported Network Boards (v1.1) Novell ships drivers on the NetWare Lite installation diskettes for the following Network Boards: ┌───────────────────────────────────────────┬─────────────┐ │ Network Board Name │ Driver Name │ ├───────────────────────────────────────────┼─────────────┤ │*Other boards │ │ │3Com EtherLink II │ 3C503.COM │ │3Com Etherlink/MC │ 3C523.COM │ │**3Com Etherlink/MC TP │ 3C523.COM │ │**3Com Etherlink II TP │ 3C503.COM │ │ │ │ │Artisoft AE-2 Ethernet Adapter │ NE2000.COM │ │IBM PC Network Baseband Adapter │ PCN2L.COM │ │IBM PC Network Baseband Adapter/A │ PCN2L.COM │ │IBM PC Network Baseband Adapter II │ PCN2L.COM │ │IBM PC Network Baseband Adapter II/A │ PCN2L.COM │ │IBM Token-Ring Adapter/A │ TOKEN.COM │ │IBM Token-Ring Network 16/4 Adapter │ TOKEN.COM │ │IBM Token-Ring Network 16/4 Adapter/A │ TOKEN.COM │ │IBM Token-Ring Network Adapter II │ TOKEN.COM │ │Novell/Eagle NE/2 │ NE2.COM │ │Novell/Eagle NE1000 │ NE1000.COM │ │Novell/Eagle NE2000 │ NE2000.COM │ │**Novell/Eagle NE1500T │ NE1500T.COM │ │**Novell/Eagle NE2100 │ NE2100.COM │ │SMC PC130 │ TRXNET.COM │ │SMC PC130E │ TRXNET.COM │ │SMC PS110 │ TRXNET.COM │ │**SMC PC270E │ TRXNET.COM │ │Western Digital EtherCard PLUS Elite │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 10T │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 16 │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 16T │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite Combo │ WDPLUS.COM │ │ │ │ │**New to NetWare Lite v1.1 │ │ └───────────────────────────────────────────┴─────────────┘ If your network board does not appear in this list, refer to your hardware documentation to determine if your board is compatible with a board that is on the list. If you find a match, you can select the compatible board type during installation; or consult your reseller for other network boards supported by Novell-certified DOS ODI drivers. Also, you may call 1-800-NetWare (638-9273), and ask for Product Information to request an ODI driver list. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite v1.1 and OS/2 v2.0 DOCUMENT ID#: FYI.P.6107 DATE: 08DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NetWare Lite v1.1 and OS/2 v2.0 This is an unsupported setup and configuration, and it is being presented as a "try at your own risk" solution document. Running NetWare Lite v1.1 SERVER and CLIENT under OS/2 2.0 Requirement 1: Getting SERVER and CLIENT to work under OS/2 requires that the Novell NetWare REQUESTER for OS/2 2.0 be installed. Besides the Requester, the update for the Requester called NSD201.ZIP must also be installed on the OS/2 system. Requirement 2: SERVER and CLIENT must be started from a unique DOS SESSION and environment. The DOS SESSION that SERVER and CLIENT must be started under has to be run from an image file; this image file is created from a bootable DOS diskette. The image file is create by using the OS/2 utility called VMDISK.EXE located in the OS2\MDOS subdirectory. This DOS diskette should also contain the following files: COMMAND.COM -- from the DOS that created the boot disk. DOSVIPX.SYS -- from the NetWare subdirectory created by the Requester. FSFILTER.SYS -- from the OS2\MDOS subdirectory created by OS/2. AUTOEXEC.BAT -- set up like shown in EXAMPLE 1. CONFIG.SYS -- set up like shown in EXAMPLE 2. Requirement 3: The DOS SESSION's "DOS settings" should be set up as follows: DOS COMMAND SETTING *1. COM HOLD OFF *2. DOS_BACKGROUND_EXECUTION ON *3. DOS_BREAK OFF *4. DOS_DEVICE empty 5. DOS_FCBS 0 6. DOS_FCBS_KEEP 0 *7. DOS_FILES 40 (Note: OS/2 has problems with DOS_FILES being greater that 45) 8. DOS_HIGH OFF 9. DOS_LASTDRIVE M (Note: This must be any letter other than Z, which is the default.) *10. DOS_RMSIZE 640 11. DOS_SHELL should be empty 12. DOS_STARTUP_DRIVE C:\DOS.img (Note: The drive letter and image file name should be what you called it and where you put the image file.) *13. DOS_UMB OFF *14. DOS_VERSION nothing selected 15. DPMI_DOS_API DISABLED 16. DPMI_MEMORY_LIMIT 0 *17. DPMI_NETWORK_BUFF_SIZE 8 18. EMS_FRAME_LOCATION NONE 19. EMS_HIGH_OS_MAP_REGION 0 20. EMS_LOW_OS_MAP_REGION 0 21. EMS_MEMORY_LIMIT 0 *22. HW_NOSOUND OFF *23. HW_ROM_TO_RAM OFF 24. HW_TIMER ON 25. IDLE_SECONDS 1 (Note: Must not be zero) 26. IDLE_SENSITIVITY 30 (Note: Must not be much greater than 30 or the CPU usage will start peaking. Use the PULSE icon to view OS/2 CPU usage.) *27. KBD_ALTHOME_BYPASS OFF *28. KBD_BUFFER_EXTEND ON *29. KBD_CTRL_BYPASS NONE *30. KBD_RATE_LOCK OFF *31. MEM_EXCLUDE_REGIONS empty (Note: You may need to set this option if your network board has a memory address that needs to be excluded.) *32. MEM_INCLUDE_REGIONS empty *33. MOUSE_EXCLUSIVE_ACCESS OFF 34. NetWare_RESOURCES NONE *35. PRINT_TIMEOUT 15 *36. VIDEO_FASTPASTE OFF *37. VIDEO_MODE_RESTRICTION NONE *38. VIDEO_ONDEMAND_MEMORY ON *39. VIDEO_RETRACE_EMULATION ON *40. VIDEO_ROM_EMULATION ON *41. VIDEO_SWITCH_NOTIFICATION OFF *42. VIDEO_WINDOW_REFRESH 1 *43. VIPX_ENABLED 44. XMS_HANDLES 0 45. XMS_MEMORY_LIMIT 0 *46. XMS_MINIMUM_HMA 0 *OS/2 DOS SESSION's default settings EXAMPLE 1: The CONFIG.SYS of the DOS SESSION should be as follows: device=fsfilter.sys shell=command.com /p /e:512 files=50 buffers=20 device=DOSvipx.sys lastdrive=m EXAMPLE 2: The AUTOEXEC.BAT of the DOS SESSION should be as follows: prompt $p$g path c:\drDOS;c:\nwlite; share c: cd\nwlite server.exe client.exe EXAMPLE 3: The NET.CFG is in the NWLITE subdirectory on the C: drive if NetWare Lite was set up as a server or client/server. It would be found on some other drive letter possibly if NetWare Lite was set up as a client only. The parameters in the NET.CFG below will not be used in the OS/2-NetWare Lite set up; however, if other parameters are needed for NetWare Lite specific functions, then the following NET.CFG would get used: # Setup the NE2000 board Link driver NE2000 INT 5 PORT 300 EXAMPLE 4: The NET.CFG in the OS/2 2.0 root directory. This is used by the requester when OS/2 is booting up to set up the network board and its environment. If network level or driver level parameters are to be added, then they should be added to the following NET.CFG file: Link Driver NE2000 INT 5 PORT 300 Protocol Stack IPX SOCKETS 100 EXAMPLE 5: The CONFIG.SYS of the OS/2 2.0 Environment The section of the NetWare Requester was added by the Requester installation process. The lines that have "<<<< NEED CHANGING" by them, should have the REMARKing change made to them if this is a NetWare Lite network only. If big NetWare is involved, then they should be left unREMARKed. PROTSHELL=D:\OS2\PMSHELL.EXE SET USER_INI=D:\OS2\OS2.INI SET SYSTEM_INI=D:\OS2\OS2SYS.INI SET OS2_SHELL=D:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE SET COMSPEC=D:\OS2\CMD.EXE LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;D: \NetWare; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INS TALL; D:\;D:\OS2\MDOS;D:\OS2\APPS;L:\OS2;P:\OS2;D:\NetWare;y:; SET DPATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\IN STALL;D:\;D:\OS2\BITMAP;D:\OS2\MDOS;D:\OS2\APPS;D:\NetWare; SET PROMPT=$i[$p] SET HELP=D:\OS2\HELP;D:\OS2\HELP\TUTORIAL; SET GLOSSARY=D:\OS2\HELP\GLOSS; PRIORITY_DISK_IO=YES FILES=40 DEVICE=D:\OS2\TESTCFG.SYS DEVICE=D:\OS2\DOS.SYS DEVICE=D:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=128,LW MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=D:\OS2\SYSTEM 4096 6144 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512; BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=OS2DASD.DMD SET BOOKSHELF=D:\OS2\BOOK SET EPATH=D:\OS2\APPS PROTECTONLY=NO SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS /P FCBS=16,8 RMSIZE=640 DEVICE=D:\OS2\MDOS\VEMM.SYS DEVICE=D:\OS2\MDOS\VMOUSE.SYS DOS=LOW,NOUMB DEVICE=D:\OS2\MDOS\VDPX.SYS DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB DEVICE=D:\OS2\MDOS\VDPMI.SYS DEVICE=D:\OS2\MDOS\VWIN.SYS DEVICE=D:\OS2\MDOS\VCDROM.SYS DEVINFO=SCR,VGA,D:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_VGA SET VIO_VGA=DEVICE(BVHVGA) DEVICE=D:\OS2\MDOS\VVGA.SYS DEVICE=D:\OS2\POINTDD.SYS DEVICE=D:\OS2\MOUSE.SYS SERIAL=COM1 DEVICE=D:\OS2\COM.SYS DEVICE=D:\OS2\MDOS\VCOM.SYS CODEPAGE=437,850 DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP REM --- NetWare Requester statements BEGIN --- DEVICE=D:\NetWare\LSL.SYS RUN=D:\NetWare\DDAEMON.EXE DEVICE=D:\NetWare\NE2000.SYS DEVICE=D:\NetWare\IPX.SYS DEVICE=D:\NetWare\SPX.SYS RUN=D:\NetWare\SPDAEMON.EXE REM DEVICE=D:\NetWare\NWREQ.SYS <<<< NEED CHANGING REM IFS=D:\NetWare\NWIFS.IFS <<<< NEED CHANGING REM RUN=D:\NetWare\NWDAEMON.EXE <<<< NEED CHANGING rem DEVICE=D:\NetWare\NETBIOS.SYS rem RUN=D:\NetWare\NBDAEMON.EXE DEVICE=D:\NetWare\VIPX.SYS REM DEVICE=D:\NetWare\VSHELL.SYS <<<< NEED CHANGING REM --- NetWare Requester statements END --- Note: The setup and settings listed above is one way that the NetWare Lite v1.1 and OS/2 2.0 have worked together. These settings may be adjusted further for better optimization depending on the system configuration being used. If the NetWare Lite SERVER.EXE is run as shown in example 2 above, this may cause a multiple NetWare Lite server environment to be slower in responding during LOGINs, MAPs, CAPTUREs, and other similar circumstances because the NetWare Lite server under OS/2 is on a time slice. This means that when a NetWare Lite command is executed, other NetWare Lite servers may need to respond and the whole network may have to wait for the NetWare Lite server running under OS/2 to respond. If only the NetWare Lite CLIENT.EXE is run, there should be no network slow down because this would only be a client machine accessing other servers on the network eliminating the slow down of clients accessing it as a server. This does not provide GLOBAL support to the OS/2 sessions; or in other words, a NetWare Lite v1.1 mapped drive letter in the above discussed DOS SESSION does not show up as an available drive in an OS/2 session. If an ARCnet, Token-Ring, or other network boards that occupy a memory address are used, then the MEM_EXCLUDE_REGIONS setting under the OS/2 DOS SESSION settings must include that memory area. A little known fact is that many EGA and VGA boards use Interrupt line 2; therefore, machines with these video boards should set up the network board with an interrupt other than 2. PORT addresses in all network boards should be 300 or greater. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Network Applications DOCUMENT ID#: FYI.P.6011 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Network Applications Installing applications on NetWare Lite may be different from installing applications on NetWare. NetWare is, as you know, a very popular LAN. Many applications have NetWare specific installation options. These installation options do not apply to NetWare Lite networks. NetWare Lite is a DOS peer-to-peer network. If the application being installed has network specific installations, then "Other networks..," "DOS peer-to-peer network," or the like should be selected. Do not select NetWare or Novell installation options. See Appendix B in the NetWare Lite documentation for more details about using NetWare Lite with NetWare. In general, some consideration should be given when installing applications. If the application requires configuration information at the time it is installed, then consideration should be given to which CLIENTs (machines) will use the application. Example: Suppose application TESTAPP.EXE is being installed and it prompts for the monitor type that will be used with this application. Suppose that the machine you are on has a VGA screen but no other machines on the network have VGA screens. If you were to select VGA then when this application is run from across the network from an CGA screen, it may not function properly. Novell has no specific guidelines on this subject, as a general solution may not be possible. This is a general problem with configurations of applications on a network. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Supported Network Boards DOCUMENT ID#: FYI.P.6015 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Supported Network Boards Novell ships drivers on the NetWare Lite installation diskettes for the following network boards: ┌───────────────────────────────────────────┬────────────────┐ │ NETWORK BOARD NAME │ DRIVER NAME │ ├───────────────────────────────────────────┼────────────────┤ │*Other boards │ │ │3Com EtherLink II │ 3C503.COM │ │3Com EtherLink/MC │ 3C523.COM │ │Artisoft AE-2 Ethernet Adapter │ NE2000.COM │ │IBM PC Network Baseband Adapter │ PCN2L.COM │ │IBM PC Network Baseband Adapter/A │ PCN2L.COM │ │IBM PC Network Baseband AdapterII │ PCN2L.COM │ │IBM PC Network Baseband Adapter II/A │ PCN2L.COM │ │IBM Token-Ring Adapter/A │ TOKEN.COM │ │IBM Token-Ring Network 16/4 Adapter │ TOKEN.COM │ │IBM Token-Ring Network 16/4 Adapter/A │ TOKEN.COM │ │IBM Token-Ring Network Adapter II │ TOKEN.COM │ │Novell/Eagle NE/2 │ NE2.COM │ │Novell/Eagle NE1000 │ NE1000.COM │ │Novell/Eagle NE2000 │ NE2000.COM │ │SMC PC130 │ TRXNET.COM │ │SMC PC130E │ TRXNET.COM │ │SMC PS110 │ TRXNET.COM │ │Western Digital EtherCard PLUS Elite │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 10T │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 16 │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 16T │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite Combo │ WDPLUS.COM │ └───────────────────────────────────────────┴────────────────┘ If your network board does not appear in this list, refer to your hardware documentation to determine if your board is compatible with a board that is on the list. If you find a match, you can select the compatible board type during installation. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Selecting "Other" Board Driver During Installation DOCUMENT ID#: FYI.P.6091 DATE: 01DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6016 SYMPTOM NA ISSUE/PROBLEM Selecting "Other" Board Driver During Installation Novell ships drivers on the NetWare Lite installation diskettes for the following network board. ┌───────────────────────────────────────────┬───────────────┐ │ NETWORK BOARD NAME │ DRIVER NAME │ ├───────────────────────────────────────────┼───────────────┤ │*OTHER BOARDS │ │ │3Com EtherLink II │ 3C503.COM │ │3Com EtherLink/MC │ 3C523.COM │ │Artisoft AE-2 Ethernet Adapter │ NE2000.COM │ │IBM PC Network Baseband Adapter │ PCN2L.COM │ │IBM PC Network Baseband Adapter/A │ PCN2L.COM │ │IBM PC Network Baseband AdapterII │ PCN2L.COM │ │IBM PC Network Baseband Adapter II/A │ PCN2L.COM │ │IBM Token-Ring Adapter/A │ TOKEN.COM │ │IBM Token-Ring Network 16/4 Adapter │ TOKEN.COM │ │IBM Token-Ring Network 16/4 Adapter/A │ TOKEN.COM │ │IBM Token-Ring Network Adapter II │ TOKEN.COM │ │Novell/Eagle NE/2 │ NE2.COM │ │Novell/Eagle NE1000 │ NE1000.COM │ │Novell/Eagle NE2000 │ NE2000.COM │ │SMC PC130 │ TRXNET.COM │ │SMC PC130E │ TRXNET.COM │ │SMC PS110 │ TRXNET.COM │ │Western Digital EtherCard PLUS Elite │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 10T │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 16 │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite 16T │ WDPLUS.COM │ │Western Digital EtherCard PLUS Elite Combo │ WDPLUS.COM │ └───────────────────────────────────────────┴───────────────┘ If your network board does not appear in this list, refer to your hardware documentation to determine if your board is compatible with a board that is on the list. If you find a match, you can select the compatible board type to complete the installation. If your board is not compatible with any of the boards listed, you will have to use the board driver supplied with the board or provide your own board driver. Any board drivers not supplied on the installation diskettes are considered to be "other" board drivers. Unfortunately, the installation program fails to complete properly if "other" is selected during installation. To install NetWare Lite with your "other" board driver, complete the following steps: Note: See Fax Document 156 or FYI.P.6089 for drivers added to NetWare Lite v1.1. 1. Make backup copies of the original "program" and "driver" diskettes. If you have a 720 KB or 1.2 MB floppy drive, you can copy both original diskettes onto one backup diskette. 2. Copy your board driver onto the backup diskette. If you made a separate backup diskette of the "program" and "driver" diskettes, you must copy the board driver to the "driver" backup diskette. 3. Begin the installation program as you normal; however, use each backup diskette instead of the original. 4. When prompted to select a network board, verify that "other" is highlighted and press <Enter>. (This is in the INSTALL step 3.) 5. When prompted to insert the diskette that contains your board driver, simply press <Esc>. Other Driver List should come up with the name of your driver now in the list. NOTE: The "OTHER" selection will only work if your driver has a .COM extension. 6. Use the arrow keys to highlight the name of your board driver and press <Enter>. 7. Continue following the installation program prompts until the program completes. 8. When the installation program completes, press <Esc> to exit. If you installed the board with nondefault settings, you will need to create a configuration file to inform IPX. The configuration file is named NET.CFG and should be located in the same directory as the other NetWare Lite program files. The NET.CFG created by NetWare Lite has the following format. Refer to your hardware documentation for information on setting up your board and what to include in NET.CFG. # Setup the NE2000 board Link driver NE2000 INT 3 PORT 300 SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Before Begining Installation DOCUMENT ID#: FYI.P.6018 DATE: 01DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Before Begining Installation NetWare Lite is designed to allow multiple computers (nodes) in a physical LAN segment (network) to share resources like printers and disk space. Computers that make resources available to the network are called servers. Computers that access resources are called clients. In NetWare Lite's peer-to-peer environment, almost any computer on the network can be a server, a client, or both. The only limitation is that a server must have a hard disk. However, there are other things to consider when deciding which computers will be servers, clients, or both. Before you begin installing NetWare Lite, take a few minutes to consider the following: ■ Which computers have printers, applications, or data that need to be shared? ■ How big or fast are the hard disks and CPUs in the computers that will be part of the network? ■ Where will the computers and printers be located? Are they close enough together for the cabling system that you plan to use? ■ What kind of network board will you use? ■ Can one of the computers be made a dedicated server to increase network performance? ■ Will any of the computers be connected to another network at the same time? ■ Which computers can be made physically secure? ■ How sensitive will information on this network be? ■ Who will be responsible for network administration? All of these items will effect whether you decide to make a computer a server, a client, or both. In general, the machines with the fastest hard disk/CPU combinations should be made servers. Installing applications on the computer with the greatest disk capacity will facilitate centralized administration and maintenance but may not be the best choice from a performance standpoint. Example: Suppose everyone on the network uses the same word processor that is installed on computer A, but only one person uses the spreadsheet application managing a large database. Because the spreadsheet application can demand large amounts of processing capacity, it would probably be better to install the spreadsheet and database on a server other than computer A. That way the spreadsheet and word processor will not have to compete for processing time. A major consideration in setting up any network is what type of cabling system (topology) will be used. The most important factor is distance between computers. Another factor is how cabling can be routed through your office or building. There are several widely used systems to choose from, each with its own advantages and disadvantages. For information on cabling and other hardware issues see the series of fax documents on "Hardware." If there is only one server in your network or a particular server does not require access to other servers' resources, then you should consider making it a dedicated server. See the fax document "Dedicated Servers" for more information on setting up a dedicated server. For information on installing NetWare Lite in a preexisting network, see the series of fax documents on "NetWare and NetWare Lite." Security requirements will also determine which computers should be servers/clients. NetWare Lite provides three levels of security to protect your sensitive data. However, it is best to physically protect computers containing sensitive material as well. This may mean having to place such computers behind locked doors. How your network is administered will contribute significantly to user satisfaction. NetWare Lite greatly simplifies network administration by decentralizing the databases used to keep track of items such as who can log in or who has privileges to what. A major feature of NetWare Lite is the ability to administer the network from any computer on the network. This means that each person who administers the network does not have to use "the server" to perform administrative tasks. For more information on administration and security, see the series of fax documents on "Network Administration." To access the fax document system, do the following: 1. Call 1-800-NET-WARE 2. Press the * key during the initial recording. The computer will then switch over to the FAX system and prompt for some information. 3. When it prompts for the FAX document number, type 100. After hanging up, the computer will call up your fax machine and send you each document requested. Note: Document 100 is an index to other documents available on the fax system. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Running a Dedicated Server DOCUMENT ID#: FYI.P.6036 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Running a Dedicated Server Network performance can be improved by running servers as dedicated. A dedicated server is one that does not run simultaneously as a client. Also, the less the server is used as a workstation the better it will perform as a server. Performance may be further enhanced by running the auxiliary utility DEDICATE.COM found in the C:\NWLITE directory. If DEDICATE.COM is not in the NWLITE directory, it can be copied from the original (or backup) product installation disk. Load DEDICATE after loading SERVER. This can be accomplished by typing DEDICATE at the DOS command prompt if C:\NWLITE is in your PATH or typing C:\NWLITE\DEDICATE if it is not. Adding this command to the STARTNET.BAT file will load DEDICATE every time you bring up the server. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: SERVER Only Instead of SERVER and CLIENT DOCUMENT ID#: FYI.P.6004 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM SERVER Only Instead of SERVER and CLIENT NetWare Lite is designed to allow multiple computers (nodes) in a physical LAN segment (network) to share resources like printers and disk space. Computers that make resources available to the network are called servers. Computers that access resources are called clients. If a particular server does not require access to other servers' resources, then you should consider making it a server only. A server that does not run simultaneously as a client is called a "dedicated" server. Network performance can be improved by running servers as dedicated. Also, the less the server is used as a workstation, the better it will perform as a server. Note that a workstation must be running as a client to use the NET utility, which is the interface for managing the network. This means that a computer that is configured as a server-only must be managed from another network workstation that is a client. See Fax Document 231 or FYI.P.6018 for more information on deciding how to set up your network. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Assisting Floppy Based Clients DOCUMENT ID#: FYI.P.6017 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Assisting Floppy Based Clients If there are workstations on the network that do not have hard disks, Novell suggests that NetWork Directories be set up to help those workstations. A DOS shared Network Directory should be created so that workstations with no hard disks can load DOS commands from the network. A Network Directory sharing IBM DOS v3.10 (named IBM_DOS_310 perhaps) would be useful for those CLIENTs with only floppy drives to get to their version of DOS. In conjunction with this, the DOS environment variable COMSPEC should be set to allow you to load COMMAND.COM from across the network. For example, the following lines could be included in an AUTOEXEC.BAT or STARTNET.BAT file: NET MAP F: IBM_DOS_310 SET COMSPEC=F:\COMMAND.COM In addition, workstations that only have floppy drives can be assisted by creating a Network Directory where the NetWare Lite utility (NET.EXE, NET.OVL, NET.HLP and LITE$RUN.OVL) can be loaded; instead of always loading them from the floppy. Novell suggests that a Network Directory called NWLITE be created. This directory should be a SERVERs C:\NWLITE directory. Novell also suggests that this Network Directory be given default rights of READ and not the default of ALL. All floppy-only CLIENTs should map a drive to this resource and add the drive to their DOS path. This will allow the loading of the NET utility from across the network, which is a much better solution than loading from floppy. For example, the following lines could be included in an AUTOEXEC.BAT or STARTNET.BAT file: NET MAP M: NWLITE PATH=M:.;%PATH% If you want to run the CLIENT from a floppy drive and have that diskette be the boot diskette, the following configuration is suggested. (Where ever NE2000.COM appears, replace it with the appropriate driver name you are using. Also, the drive letters L: and M: are simply used as examples; you may use any other valid driver letters. Drive M: is mapped to the Network Directory NWLITE as described above. Similarly, Drive L: is mapped to the Network Directory IBM_DOS_310 as described above.) 1. Create a bootable diskette using the FORMAT A: /S command. 2. Copy the following NetWare Lite files to the diskette: LSL.COM NE2000.COM IPXODI.COM CLIENT.EXE NET.EXE NET.CFG 3. Create an AUTOEXEC.BAT with the following lines added to it: LSL NE2000 IPXODI A CLIENT NET LOGIN NET MAP L: IBM_DOS_310 NET MAP M: NWLITE PATH=L:\;M:\;%PATH% SET COMSPEC=L:\COMMAND.COM 4. Create an CONFIG.SYS with the following line added to it: LASTDRIVE=M For those Network Directories that contain applications (executables), the drives used to map to these applications should be included in the DOS environment variable PATH. For example, the following lines could also be included in an AUTOEXEC.BAT or STARTNET.BAT file: NET MAP G: TURBOC NET MAP H: WORDPERFECT NET MAP I: GAMES SET PATH=G:\BIN;H:.;I:\TETRIS;%PATH SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: SHARE.EXE: Status Report 5 DOCUMENT ID#: FYI.P.6003 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM SHARE.EXE: Status Report 5 When loading the server, you may get "Status Report 5," which talks about SHARE.EXE not being loaded when the SERVER.EXE was executed. SHARE.EXE is a program that comes with DOS 3.1 or above. SHARE is the mechanism that allows files to be accessed simultaneously from multiple clients. If you get a "Status Report 5" message, you do not have SHARE.EXE in your PATH. Add the appropriate directory to your PATH (where SHARE.EXE is located), or copy SHARE.EXE to the directory where NetWare Lite is installed. Although loading SHARE is not required for the server to run, it is strongly recommended. SHARE should be loaded before SERVER. SHARE should be tuned for proper performance. You may need to increase the values for locks (/L) and files (/F) if you run database applications or if you have more than four users accessing the server. See your DOS documentation for more information on configuring SHARE. You do not need to load SHARE before loading CLIENT. When you increase the number of files that can be locked at one time (example, by increasing the /L: above the default of 20), you must also increase the amount of file space in the operating system's storage area by increasing the /F: above the default of 2048. Generally, each open file requires an additional 20 bytes of storage space. See your DOS documentation for more information. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing (Possible Solutions) NetWare Lite v1.1 DOCUMENT ID#: FYI.P.6108 DATE: 07DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Printing (Possible Solutions) NetWare Lite v1.1 Before going any further, if you have not applied patches for NetWare Lite v1.1, please get Fax Document 265 or FYI.P.6115, read it, and acquire the most current applicable patch file. ***** WARNING ***** The following information is about printing problems you may come across. Though every effort is made to confirm these solutions, they may not work in every case. With the variety of possible causes of print problems, Novell cautions you to make a backup of your data before trying any of these suggestions. Also, all information is about NetWare Lite v1.1 only. If you have not already done so, please upgrade to NetWare Lite v1.1. If you have already upgraded from NetWare Lite v1.0 to v1.1 and are having printing problems, a possible solution is to physically delete the network printer files and network printer definition and recreate the definition using NetWare Lite v1.1. Do the following steps to make the necessary changes: 1. Go to DOS and make sure that you are on your C: drive. 2. Change to the NWLITE directory by typing CD\NWLITE 3. Change to a hidden directory called NLCNTL by typing CD NLCNTL 4. There will be a directory for each printer on your machine. Delete the contents of the directory, and then delete the directory. (The name of the directory may be SLPT1, SLPT2, SLPT3, SCOM1 or SCOM2.) The following are examples of how to delete the files and directories: Using DR DOS 6.0: XDEL SLPT1 /RSD Using MS-DOS 5.0: DEL SLPT1\*.* RD SLPT1 Note: Do not delete any files in the NLCNTL directory. Only delete the files in the directories for the printers as outlined above. 5. Change back to the NWLITE directory by typing CD.. 6. Type NET 7. Go to "Supervise the Network," then to "Network Printers." 8. Delete your network printer. 9. Recreate your network printer. (See the printer setup below) 10. Exit the NET UTILITY. Note: You may set Capture settings under Network Printers, if you wish, before Exiting or continue with step 11 below. 11. Capture your network printer. 12. Print a file from DOS with the network loaded (COPY C:\AUTOEXEC.BAT LPT1). 13. Print a file from your application. Printer Setup If you are having printing problems, Novell presumes that the Network Printers are not setup properly. Because this has been the source of some confusion, it is necessary to check this information first. To do so with the Network running (server loaded and supervisor logged in), do the following: 1. Type NET 2. Select "Supervise the Network," 3. Select "Network printers." 4. If a printer does not exist, do the following: a. Press the <Insert> key, and a list of existing servers will come up. b. Select the server where the printer is physically located. c. Enter a printer name. (Novell recommends using a name that will identify the printer such as HP_LASERJET_III.) 5. Then select a port to which the printer is connected. 6. The next screen shows default information for the printer. At this point you can press <F1> for information and details of each option. 7. You may now escape out of NET (press <Esc> several times until an EXIT message comes up); EXIT; and reboot your server. After you are back up and running, you can issue your NET CAPTURE statement to specify the port and printer name and any other valid capture parameters. (See the NetWare Lite manual for details on NET CAPTURE; or at the DOS prompt, type NET CAPTURE ? for help information. Additional printing information can be found in Fax Document 240 or FYI.P.6025.) Questions and Answers Q1. How do I eliminate the banner page at the beginning of each print job? A1. The Banner default is set to Y(yes). Eliminate the banner by putting the following command in your Net Capture statement: b=n Q2. Each print job ejects a blank page when it finishes. Can I eliminate this wasted page? A2. Yes. The formfeed default is set to y(yes). Turn it off by putting the following command in the Net Capture statement: f=n Q3. Can I capture to a printer on my Client only machine? A3. No. You can only capture to a Server or Server-Client. Q4. I have two people sending print jobs at the same time. When the files print they get mixed up. Some of each job prints are on the same page. How can I prevent this? A4. Make sure you are not printing directly to the printer port. The default is NO; however, it can be set to d=y. When the default is set to yes, it sends the print job as soon as it gets it in the buffer and does not wait until the entire job is buffered. This first portion may print out, and then SERVER has to wait for the rest of the job. A second job sent directly may print part of its job and start mixing the two together. The jobs in turn wait for the rest of the print job from the sending application but continue mixing up the printing. If this is seen, do not use d=y. Q5. How come my printing comes out with just a few lines per page? A5. This can be caused from too small of a buffer size or wait time specification or both. ■ First, increase the w=xx parameter in Net Capture. The default is 10. However, if the print job is large or has many printing codes, graphics or postscript, the system may need more time to send the job to the buffer before the "Wait time" is exceeded and assumes that the last of the job has been sent and issues an end of file to close the job. If this happens, you may see the job split up into several jobs in the NET utility. ■ Second the print buffer may need to be increased by doing the following: 1. Go into NET. 2. Select "Supervise the network." 3. Select "Server Configuration." 4. Select your SERVER. 5. Increase the Print buffer size in the Future column. 6. Press <Esc> until you get the command line prompt. 7. Reboot the system for the changes to take effect. Note: Do not use d=y and w=0. If you set w=0, it will rely on the application to close the file. If it does not, then no printing will occur and the print job will remain open until it is closed explicitly. You will need to do this manually by sending a ^L to the port. (Hold down the <Ctrl> key and press <L> key) Example: ECHO ^L >lpt1 Q6. When sending a print job, only a few pages print out, then the printer stops, and then machine with the printer attached to it locks. What can I do to prevent this? A6. First check the WAIT parameter. Try increasing w=xx in NET CAPTURE. Also check for the presence of Caching utilities. Make sure only one is loaded. Two caching utilities loaded at the same time will conflict with each other and cause unpredictable results. If the problem persists, remove all caching and any TSRs loaded, other than the NetWare Lite files. Q7. I have just run the UPGRADE utility to NetWare v1.1. Now, print jobs are okay for the first page or two; then it prints just a few characters per page until the job is finished. Increasing the WAIT time and print buffer size does not help. What can I do? A7. Do the following to solve the problem: 1. Go to NET. 2. Select "Supervise Network." 3. Select "Network Printer." 4. Check the Characters per second. 5. If it is set at 0, change it to 16384, which is the default. Q8. The system sent a message displaying "Printer off line" or "Printer out of paper;" however, neither case is true. There is plenty paper, and it may continue printing without problem. How can I resolve this issue? A8. Increase the Error wait time by 10 to 15 seconds by doing the following: 1. Go to NET. 2. Select "Supervise Network." 3. Select "Network Printer." 4. Add 10 to 15 seconds to the current Error wait time. Q9. The server locks up intermittently when printing or the print job just disappears without printing. What can I do to prevent this? A9. Make sure there are no hardware conflicts. If using LPT1, do not use a network board set at I/O address of 360. The size of the address overlaps with the LPT1 port address of 378. If you use LPT2, do not use interrupt 5. See Fax Document 212 or FYI.P.6054 for more information on resolving I/O and IRQ conflicts. Q10. What is a typical value to set for "Characters per second"? A10. Normally, the default of 16384 is sufficient. If it is set high, then DOS will be interrupted more often to retrieve characters from the print buffer. If the printer is a serial printer or a slow machine, increasing this parameter may not affect the speed of the printer; however, it can affect the DOS foreground process. A good rule of thumb for setting "Characters per second" for serial printers is the printer baud rate divided by 10. Example: 9600 baud / 10 = 960. This parameter is a value you may need to experiment with and do some fine tuning. Q11. I have several applications from which I print different types of files. Most applications are okay but a few of them print odd formats, ASCII type characters, or just plain garbage. What can I do to resolve this problem? A11. Make sure the NetWare Lite v1.1 patches are installed as specified at the beginning of this document. CLPRNTR.PAT is the patch that will most likely be needed. Q12. When I print from my Client to a printer attached to my Server-Client, it prints just fine. However, if I print from my Server-Client to the same printer, the data is corrupted and sometimes the Server-Client machine locks. I also have noticed many lost clusters on my hard drive and sometimes problems with the drives File Allocation Table (FAT) table. What causes this and how can I solve it? A12. This is a known problem relating to NetWare Lite. Use INT28FIX.PAT. See the patch information at beginning of this document for explanation. Q13. My application is setup to output to a COM port. How can I CAPTURE the port and send the print job to a printer on my server? A13. NetWare Lite will not CAPTURE to a COM ports. If the application is hard coded to print to a COM port, you will need to work that out with the application manufacture. If the application configuration can be changed to output to an LPT port, then do so and CAPTURE the LPT port. This may be the problem if you get redirect errors. Example: If printer LaserJet is attached to the server and the CAPTURE command is executed from a client, the following will occur: Net Capture COM1 Laserjet (Will not work) Net Capture LPT1 Laserjet (Will capture the LPT1 port of the client and end the print job to the Laserjet attached to the server machine) Q14. I run NetWare Lite and Windows and other various applications. When I send a print job from the application, it will go on hold until I exit out of Windows. Then it prints without flaws. What causes it to hold until I exit Windows? A14. First, check the Windows SYSTEM.INI file in the [shell] section. If the application is listed there, remove it from this area and try again. Second, see Fax Document 204 or FYI.P.6095 for possible solutions. Q15. All print jobs are printing extremely slow. A15. First, try printing from DOS without any NetWare Lite files loaded. In most cases, the slow down is related to bad or conflicting hardware. Check for the use of any A-B switches or multiplexor hardware connected to the port. If any of these items is in use, remove it and try printing. If it is still slow, the problem may be that the port itself is bad. If it prints fine without NetWare Lite but as soon as Lite is loaded the slow down occurs, you may need to adjust the print buffer size and try fine tuning the "Characters per second" parameter. Q16. When I try printing, the system displays an error 5 (access denied). Sometimes, the message displayed says "error writing to disk, there may not be enough space on the disk (disk full messages)" even though the disk has several megabytes available. A16. The software used may be calling for the attributes of a device and getting the wrong information from NetWare Lite. Use OPENDEV.PAT from the previous mentioned patches. Q17. Can I set up my printer on my Server-Client machine as a NetWare Lite printer and print to it using Net Capture as well as use it as a DOS printer? A17. No. If the printer is set up in the NET utility as a Network printer and Server is loaded, then NetWare Lite has control of the printer; and it is no longer available to DOS. Be sure to NET CAPTURE the port first, then you may print to it. If you print directly to the printer without capturing, you may corrupt the print job. Q18. Can I NET CAPTURE a nonexistent port such as LPT2 so I can use LPT1 for DOS printing. A18. Yes, provided your machine is not a Server as was covered in the previous question. EXAMPLE: Net Capture lpt2 Laser (If LPT2 does not exist and applications send their print output to the LPT2 port, the print job will be redirected to printer Laser that is attached to a Server machine, and LPT1 will be free for DOS use.) Q19. I can have Net Capture loaded but cannot do a print screen or redirect an ASCII file to the LPT port. Also, some applications do print okay while others do not. What causes this? A19. This may happen if the printer can be set to different print modes. Example: a HP Laserjet IIIsi can be set to PCL or Postscript mode. If the previous mentioned problems occur, check the printer and make sure it is not set to Postscript. The reason some applications work is that they may have been sending Postscript print jobs. If you are sending Postscript, make sure the NET CAPTURE contains the following parameters. ■b=n(no banner) ■t=0(no tabs) ■f=n(no formfeed) ■s=default (the default setup string should not have any values when used for postscript printing) SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Windows 3.1 Compatibility DOCUMENT ID#: FYI.P.6061 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Windows 3.1 Compatibility Installing a Stand Alone version of Windows on a NetWare Lite Network: If you are upgrading from a previous version of Windows to Windows 3.1, Novell recommends that you delete the previous version of Windows from your hard drive before you begin installing Windows 3.1. This is recommended because Windows 3.1 handles many of the settings in the initialization files (*.INI) differently than before and will not always convert these parameters to the new format. Follow the regular installation procedures to install Windows 3.1 as a stand alone version. To be able to access network resources, run the setup program and select "Microsoft Network (or 100% Compatible)" as the network. For more information on running Windows 3.1 on a NetWare Lite network, refer to the "Tips for Running Windows 3.1" section of this document. Installing a Network Version of Windows 3.1 on a NetWare Lite server: The following is intended for users who want to install windows in shared mode. Please refer to the Getting Started with Microsoft Windows booklet, pages 6 to 12. 1. Select the server on which you want Windows to reside physically. Note: Approximately 16 MB of hard disk space must be available on the server to install a shareable copy of Windows 3.1. 2. Insert the Windows DISK 1 in the disk drive, and go to that drive (Example a: <Enter>). 3. Type SETUP /A. When Windows asks for the path to which it should install, enter C:\WIN31. (If this directory does not exist, Windows will create it for you.) As you follow the prompts, a shareable copy of Windows will be installed on the server. Note: This will not create an executable copy of Windows. It merely creates a location where clients can pull the executable programs from after they have been set up (See steps for clients, below). After the shared copy of Windows has been installed, the following steps must be taken to properly configure the network software on the server. 4. Enter the NetWare Lite menu utility, by typing NET and pressing <Enter>. Then select "Supervise the network" and then "Network directories." Create a network directory by pressing the <Insert> key. Select the server where the WIN31 directory is located, type a name for the network directory, then enter the path as C:\WIN31. Press <Esc> to exit and save the changes. 5. Enter the NET menu utility. Select "Supervise the Network." Select "Server Configuration." The CLIENT TASKS option defaults to 10 at the time of NetWare Lite installation. Increase CLIENT TASKS=XX by 15 per machine connected. 6. When NetWare Lite is installed, the FILES=xx in the CONFIG.SYS file is set to be at least 30. This needs to be increased on the server by 20 per machine connected. 7. After you have performed these steps for the server, reboot the computer. The Following Steps are for the Client: There are three ways to install Windows from the shared copy installed on the server, from the steps above. Please refer to page 7 in the Getting Started with Microsoft Windows for a further explanation of the three methods. The three ways are the following: 1. Copy all files to the Client machine's hard drive. a. Load NetWare Lite by typing STARTNET. Map a drive to WIN31 by typing the following and pressing <Enter>: Net Map I: WIN31 b. Change to the I: drive by typing I: and pressing <Enter>. c. Type SETUP, and press <Enter>. Follow the prompts to install a copy of Windows to your local drive. When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Refer to Windows documentation for questions regarding the installation. You will now run Windows from your local drive, not from the I: drive. Verify that the path on your local drive that you selected in SETUP is in your AUTOEXEC.BAT file because you will need this to run Windows. 2. Custom configuration files are copied to the Client machine's hard drive. All other files will be run from the shared copy installed on the server in the steps above. a. Load NetWare Lite by typing STARTNET. Map a drive to WIN31 by typing the following and pressing <Enter>: Net Map I: WIN31 b. Create a subdirectory on the Client's hard drive in which to put the custom files Example: Type MD C:\DAVE, and press <Enter> c. Go to the network drive containing the Windows files, by typing I: and pressing <Enter>: d. Type SETUP/N, then follow the Windows installation instructions. When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Note: At the prompt for the path of the Windows files, enter the subdirectory that you created in step 2b (Example: C:\DAVE). Also, at the configuration screen, select the "Microsoft Network (or 100% Compatible)" Network option. e. When Windows prompts you, choose to review and edit the changes in the AUTOEXEC.BAT file. Verify that your user subdirectory (C:\DAVE) and I: drive have both been added to your PATH statement. f. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS, or LPT2.DOS, instead of the normal LPT1 and LPT2 ports. (See Question 3 at the end of this document.) When installation is complete, exit to DOS and reboot the machine. When you reboot the machine, DOS will give you a message similar to the following (the message differs depending on the version of DOS you are using): ┌───────────────────────────────────┐ │Search path contains invalid drive.│ └───────────────────────────────────┘ This message will occur any time you run a program and DOS searches your path. It does this because Windows inserted the I: drive into your path when it was installed. When the machine is first booted, the I: drive has not been mapped yet, so NetWare Lite is unable to locate it. Just ignore the message. When you map the I: drive to WIN31, the message will no longer be valid. If you want the error message to disappear, append I: to the end of the path after mapping the network drive or insert the following message into your AUTOEXEC.BAT file before the path statement: C:\DRDOS\SUBST I: C: (or type c:\name of DOS directory\SUBST I: C:) This line will make the I: drive temporarily look at the C: drive; thereby, making it a valid statement in the path. As soon as your map command executes, the I: drive will be redirected to a network directory. After you reboot, load the network by typing STARTNET. Then, once you have performed your drive mappings and printer captures, you can type WIN to enter Windows. 3. No files will be stored on the Client machine's hard drive. Instead, the custom configuration files will be stored in a subdirectory on a network server and all other files will be run from the shared copy of Windows installed on the server in the steps above. a. Load NetWare Lite by typing STARTNET. Map a drive to WIN31 by typing the following and pressing <Enter>: Net Map I: WIN31 b. Create a subdirectory on the Server's hard drive in which to put the custom files by typing something such as the following and pressing <Enter>: MD C:\STEVE c. Create a network directory that looks at the user's subdirectory. Enter the NetWare Lite menu utility by typing NET and pressing <Enter>. Then select "Supervise the network," then "Network directories." Create a network directory by pressing the <Insert> key. Select the server on which you want to store your custom files, then enter the path of the subdirectory you created in step b, such as C:\STEVE. d. Map a drive to this network directory by typing the following and pressing <Enter>: NET MAP G: STEVE e. Go to the network drive containing the Windows files by typing I: and pressing <Enter>: f. Type SETUP/N, then follow the Windows installation instructions. When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Note: At the prompt for the path of the Windows files, enter the drive you have mapped to the custom files network directory from step d, above (in this example it would be G:). Also, at the configuration screen, select the "Microsoft Network (or 100% Compatible)" Network option. g. When Windows prompts you, choose to review and edit the changes in the AUTOEXEC.BAT file. Verify that the G: and I: drives have both been added to your PATH statement. h. Follow the prompts to continue the installation of Windows. When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS or LPT2.DOS instead of the normal LPT1 and LPT2 ports. (See Question 3 at the end of this document.) After the installation has completed, choose "Return to DOS," and reboot the machine. When you reboot the machine, DOS will give you a message similar to the following (the message will differ depending on the version of DOS you are using): ┌───────────────────────────────────┐ │Search path contains invalid drive.│ └───────────────────────────────────┘ This message will occur any time you run a program and DOS searches your path. It does this because Windows inserted the I: drive into your path when it was installed. When the machine is first booted, the G: and I: drive had not been mapped yet, so NetWare Lite was unable to locate them. Just ignore the message. When you map the I: drive to WIN31, the message will no longer be valid. If you want the message not to appear, append I: and G: to the end of the path after the network drives have been mapped or insert the following messages into your AUTOEXEC.BAT file before the path statement: C:\DRDOS\SUBST I: C: (or type c:\name of DOS directory\SUBST I: C:) C:\DRDOS\SUBST G: C: (or type c:\name of DOS directory\SUBST G: C:) This line will make the G: and I: drives temporarily look at the C: drive, thereby making them valid statements in the path. As soon as your map command executes, the G: and I: drives will be redirected to network directories. When you reboot, load the network by typing STARTNET. Then, when you have performed your drive mappings and printer captures, type WIN to enter Windows. TIPS FOR RUNNING WINDOWS 3.1: Network Operations Start the NetWare Lite environment before running Windows (for example: make sure all drives are mapped, printer ports are captured, and network resources are set up). Using Windows to Perform Network Operations If you have a connection to a server, either a captured port or mapped drive, you will be able to perform your network operations with no problems. The File Manager will let you access previously mapped drives without problems. If you selected "Microsoft Network (or 100% compatible) in the Windows setup, the File Manager and Print Manager (as well as Printers in the Control Panel) will include options for capturing network printers and mapping network drives. Note: If you do not have a connection (either a mapped drive or a captured port) to a server before you enter Windows, you will get a Network Error if you try to access it in the File Manager or Print Manager. If you get errors in Windows trying to perform drive mappings and printer captures when you exit Windows, you will no longer be able to execute the NET MAP or NET CAPTURE commands until you reboot your computer. Mapped Drives and Connections Windows will display an error message if you try to access a drive on a server that has gone down. Any attempt to access that drive will fail. Under regular DOS, this error is trapped and the Client saves enough information to automatically restore the connection to that network directory when the downed server returns to the network. Windows prevents regular DOS from trapping this error. To restore connections to your mapped drive, exit Windows and reissue the NET MAP command when the server is back on the network. (See Question 2 in the Q and A section of this document for more information.) Selecting Printers If you want to print from Windows to a network printer, you must set up the printer in Windows as a printer on port LPT1.DOS (which replaces LPT1.OS2 in Windows 3.0) or LPT2.DOS, depending on which port is captured. This is to instruct Windows that it is to use the information that DOS provides it (such as a NET CAPTURE command you may have issued to print to the network printer) to print to LPT1 instead of trying to go to its own physical LPT port. (Please see Question 3 in the Q and A section for more information.) Note: Do not use the print manager if printing from multiple windows. If the print manager is running, it will combine the print jobs into one document before it passes the information to NetWare Lite. Browse The browse function does not work when trying to attach to servers or trying to capture printers. NetWare Lite Messages Messages sent to network users through NetWare Lite will not be received if the user to whom you are sending the message is in Windows. Windows Modes If you are experiencing a problem that only occurs when NetWare Lite is loaded and the problem seems unsolvable, experiment with the other Windows mode to see if the problem is corrected. The Windows mode can be changed by using one of the following command line parameters: Standard Mode: WIN /s Enhanced Mode: WIN /3 (Note that Windows 3.1 does not include an option to run in Real Mode like version 3.0.) Permanent Swap Files Windows 3.1 can use swap files to enhance the performance of multiple tasks. By default, Windows will try to create a swap file on your hard disk at installation. Do not create a permanent swap file on a network drive. It will corrupt any other swap file that may be on that computer. If you do not have a local hard disk on which to store a permanent swap file, it is recommended you use a temporary swap file in your user subdirectory on the network. This will avoid conflicts between two users' permanent swap files. (Note: If you are running a shared version of windows on the server, you should MAP drives to the network directories and should not use the DOS SUBST command. This is unique to Windows 3.1. In all other applications, using the DOS SUBST command on a server in place of the NET MAP command is recommended). Using DR-DOS 6.0 If you are using DR-DOS 6.0, you must first install the December 1991 update followed by the April 1992 update (installed in that order) to run with Windows 3.1. Contact Novell technical support for questions regarding this issue. Interrupts VPICDA.386 is a patch written by Microsoft that fixes problems that arise when network boards are set to an interrupt of 2, 3, or 9 and above for use with Windows 3.0. Microsoft states that you no longer need this patch with Windows 3.1. If you come across problems using these interrupts, check to see if you have a conflict with some other device using the same interrupt. (See Fax Document 212 or FYI.P.6054 for information on interrupt and I/O address conflicts.) Base I/O Addresses I/O addresses below 300 should not be used for network boards on machines that also use Windows. Changes to SYSTEM.INI Make sure that the following line is in the Windows SYSTEM.INI file: [386Enh] UniqueDOSPSP = ON This parameter controls the way Windows allocates memory to DOS applications running in Windows and is recommended by Microsoft to be set if Windows is run on some networks. Setting this parameter will solve occasional problems with applications that hang a Windows client. Another option may need to be set in the SYSTEM.INI file depending on the type of network board you are using. If you have a network board that uses a shared memory address (RAM address or memory address), that address needs to be excluded from available memory so that Windows does not assign the address to another application. Excluding this address can be done in two ways: 1. In the CONFIG.SYS file, if you load the device driver EMM386.EXE or EMM386.SYS, you need to set a parameter to exclude the memory address as shown: MS-DOS 5.0 format: DEVICE=C:\path\EMM386.EXE X=nnnn-mmmm DR-DOS 6.0 format: DEVICE=C:\path\EMM386.SYS /E=nnnn-mmmm These are sample lines from the CONFIG.SYS file where the address to be excluded is from nnnn to mmmm. The nnnn is a hexadecimal number for the starting address of the network board. The mmmm is the ending address to exclude. Most network boards use either 8 KB or 16 KB (sometimes less). The following are sample values for nnnn and mmmm addresses based on the addresses that boards can usually use. Starting address nnnn 8 KB 16 KB C0000 C000 C1FF C3FF C8000 C800 C9FF CBFF D0000 D000 D1FF D3FF D8000 D800 D9FF DBFF CC000 CC00 CDFF CFFF Note: If you are not sure whether your network board uses 8 KB or 16 KB of memory, use the 16 KB value. Using these numbers, if your memory address for your network board is C0000h and you are using MS-DOS 5.0, your EMM386.EXE line would have a similar format as the following: DEVICE=C:\DOS\EMM386.EXE X=C000-C3FF. 2. If you do not have an EMM386.EXE or EMM386.SYS driver in your CONFIG.SYS file, you can either add it using step 1 as your example or you can do the following: Edit your SYSTEM.INI file (located in your configuration file directory if you are using a shared version of Windows or in the Windows directory if you are using a stand alone version). Go down through the file until you see the section that starts with "[386Enh]" at the left margin. Add a line that says the following: EMMExclude=nnnn-mmmm The nnnn is the starting address to exclude, and the mmmm is the ending address to exclude. See the table in step 1 for more information on these values. Do not worry if you already have another EMMExclude line in the SYSTEM.INI file. Just add another one. Multiple lines in this format are valid and will not cause problems. Changes to WIN.INI There are several options you can set in the WIN.INI file for network control. NetWare Lite does not require using anything other than the default values for these options, unless you have a special need. Consult your Windows documentation for further information if you wish to change these options. Speed Issues with NetWare Lite and Windows See the fax document concerning the patches that have been released by Novell that increase printing speed. If your network printing seems slow, these patches could solve your problem. Running a large application such as Windows as a shared version has the advantage of not using up as much hard disk space. However, running Windows as a shared version will slow it down somewhat because many of the files will be in use by more than one machine at a time and access across a network will be slower than access to your own hard drive. NetWare Lite and Windows: Common Questions and Answers. Q1: Why do I get Sharing Violations and/or lockups when I'm running Windows or Windows' applications? A1: You may have neglected to set all applications (.EXE, .COM and .OVL files) to read only using the ATTRIB command. This can be done by executing the following commands in all directories that might be used across the network: attrib +r *.exe attrib +r *.com attrib +r *.ovl Q2: What happens if I lose connections while I am in Windows? A2: If a client loses connections temporarily with a server while in DOS, then one of two things will happen: 1) The connection will be reestablished by NetWare Lite. 2) The user will try to perform something that requires a connection and will get an A)bort, R)etry, F)ail error. If the user presses F) or R), then the connection will be reestablished. Unfortunately, Windows will not recognize this "critical error message," so it will not reestablish connections when attempting to perform a network operation such as printing to a network printer. The user must exit out to DOS, then perform a function that will reestablish connections after the server is back up (example DIR on a network directory) and then enter Windows again. Q3: Why do I have to select LPT1.DOS and LPT2.DOS instead of LPT1 and LPT2? A3: NetWare Lite is a peer-to-peer network, which means it runs on top of DOS. When a printer is captured, NetWare Lite tricks DOS into printing to another location (such as to a printer on another machine). This is why you can print from an application to LPT1, and the job will end up at another machine's printer. Some applications (like Windows) bypass DOS and print directly to the LPT port. So, if you print an application in Windows, it will bypass DOS that means it will bypass your capture command and will try to print to a printer on your client (instead of where you want it to go). However, you can trick Windows by going into the WIN.INI file and under the [Ports] section inserting the following line: [Ports] LPT1.XXX= (The suffix can be any three letters.) For example: LPT1.DOS= Windows now recognizes that there is a file called LPT1.DOS on your disk. If you select LPT1.DOS in "printer setup" under Control Panel, Windows will try to print to this "file." When Windows sends a print job to the file "LPT1.DOS" to DOS, DOS strips off the suffix (DOS, XXX, or whatever), and sends the job to the redirected printer. Q4: Why can't I print using WordPerfect for Windows? A4: If WordPerfect printer drivers are being used instead of Windows', the user needs to make some adjustments to make WordPerfect work correctly. The adjustments are similar to the ones made above to Windows. First, go into select printer. Rather than selecting LPT1 or LPT2, select "file." Then enter the name of a file that starts with LPT1 or LPT2: For example: LPT1.DOS This will cause WordPerfect to print to LPT1 correctly for the same reasons it enables Windows to work correctly. Q5: Why in the File Manager do I sometimes get Network Errors and my network directories appear to have no files in them? A5: If you try to use the File Manager's features to connect to network directories on a server to which you do not have an active connection (either a mapped drive or a captured port) before you enter Windows, any attempt to connect to that server in the File Manager will result in these error conditions. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Cabling Specifications DOCUMENT ID#: FYI.P.6064 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6013 SYMPTOM NA ISSUE/PROBLEM Cabling Specifications and Limitations This document covers the cable installation and configuration rules for each network type including Ethernet, ARCnet, and Token-Ring. The cabling discussed includes only the most common cable types such as Thin Ethernet, Twisted-Pair Ethernet, ARCnet (coax), and Token-Ring. Ethernet Network Ethernet is a high-speed linear bus network. It can use coaxial, twisted-pair, or fiber optic cables. Thin Ethernet Cabling Thin Ethernet cabling uses RG-58/U, 50-ohm coaxial cable in a bus configuration that is a single length of cable (trunk segment) with a terminating resistor on each end. Each node (PC) attaches to the cable through a T-Connector that attaches to the BNC connector on the network board. Use the following rules for thin Ethernet cabling: ■ The network board must be set to use the BNC connector. ■ Thin Ethernet cable is RG-58/U, 50-ohm coaxial cable; no other type of cable should be used. The cable should be prepared by the factory or a trained professional because homemade cables can create problems on the network. ■ Both ends of the trunk segment must be terminated with a terminating resistor matching the rating of the cable (50 ohm). The terminator is connected to the T-Connector at the end of the segment. One end of the cable must also be grounded through a grounding terminator that must be connected to a true ground. ■ The network board is connected to the trunk segment through a T-Connector. The cable can never be plugged directly into the network board. ■ A trunk segment cannot exceed 185 meters (607 feet). ■ Up to five trunk segments can be connected through four repeaters. A repeater counts as a node on the network. ■ The entire network trunk cannot exceed 925 meters (3,035 feet). ■ The minimum cable distance between stations must be 0.5 meters (1.5 feet). ■ Avoid placing the cable on or near any electrical devices that could cause interference on the line (such as florescent lights or electric motors). ■ NetWare Lite only supports a total of 25 nodes on the entire network. Twisted-Pair Ethernet Cabling Twisted-Pair Ethernet cabling, also known as 10BaseT, uses twisted-pair cables (similar to telephone wire) in a star-shaped configuration. Each node (PC) attaches to a concentrator through a twisted-pair cable using RJ-45 connectors (similar to a telephone jack). Some network boards, specifically designed for twisted-pair use, include an RJ-45 jack instead of a BNC connector. However, standard Ethernet boards require an external device attached to the DIX connector to use this type of cabling. Use the following rules for twisted-pair Ethernet cabling: ■ Maximum segment length (unshielded): 100 meters (328 feet) ■ Maximum number of trunk segments: 1,024 ■ Maximum number of repeaters: 4 ■ Avoid placing the cable on or near any electrical devices that could cause interference on the line (such as florescent lights or electric motors). ■ NetWare Lite only supports a total of 25 nodes on the entire network. ARCnet Network ACRnet is a token-passing star bus network that connects each node to an active or passive hub through coaxial cable. The cable can also connect one active hub to another hub. These hubs act as signal splitters. Active hubs also act as signal amplifiers. ARCnet Cabling (Coax) ARCnet cabling uses RG-62/U, 93-ohm coaxial cable in a star configuration. Each node (PC) is connected to an active or passive hub with one end of the cable plugged directly into the BNC connector on the network board and the other end plugged into the BNC connector on the hub. If only two nodes are on the network, the cable can directly connect the two machines. If more than two nodes are on the network, an active or passive hub must be used. Use the following rules for ACRnet cabling: ■ ARCnet cable is RG-62/U, 93-ohm coaxial cable; no other type of cable should be used. The cable should be prepared by the factory or a trained professional because homemade cables can create problems on the network. ■ Unused nodes of a passive hub must be terminated using a 93-ohm terminator. Unused active hub nodes need not be terminated. ■ A passive hub cannot be connected to another passive hub. ■ Passive hubs can only connect a node and an active hub, never two active hubs. ■ Make sure that the node address of the network board in each PC is unique. This only applies if the node address is configurable. ■ Maximum cable distances depend on what you are connecting, as shown in the following chart: ┌──────────────┬──────────────┬──────────────────┐ │ FROM │ TO │ MAXIMUM DISTANCE │ ├──────────────┼──────────────┼──────────────────┤ │ Network Node │ Network Node │ 2,000 feet │ │ Network Node │ Active Hub │ 2,000 feet │ │ Network Node │ Passive Hub │ 100 feet │ │ Active Hub │ Active Hub │ 2,000 feet │ │ Active Hub │ Passive Hub │ 100 feet │ └──────────────┴──────────────┴──────────────────┘ ■ The cable length distance between the farthest two nodes in the network cannot exceed 20,000 feet. This is the maximum distance a signal can travel on the cable in the allotted time of 31 microseconds. ■ Avoid placing the cable on or near any electrical devices that could cause interference on the line (such as florescent lights or electric motors). ■ NetWare Lite only supports a total of 25 nodes on the entire network. Note: Some ARCnet boards can be connected using a bus configuration similar to thin Ethernet. For this type of board, contact your dealer for information regarding the configuration rules and specifications. Token-Ring Network Token-Ring is a token-passing network. Each node (PC) attaches to a device called a multistation access unit (MAU or MSAU) that sends the token from one node to the next node in line. A token-ring network can use either a small movable cabling system or a large nonmovable cabling system. This document will discuss the small movable cabling system. Token-Ring Cabling Token-Ring cabling uses IBM type 6 cable in a ring configuration. Each node must attach directly to a MAU. Each MAU can connect to another MAU through a patch cable to form a ring. If the total number of nodes on the network is less than or equal to eight (the number of connections on the MAU), only one MAU is needed. Adapter cables and patch cables are the two types of cables used in a Token-Ring network. Adapter cables are 8-foot IBM type 6 cables. Use an adapter cable to connect nodes directly to a MAU or to a patch cable that is connected to a MAU. Patch cables are also IBM type 6 cables and come in four lengths: 8, 30, 75, and 150 feet. A patch cable can extend the cable's distance past the 8-foot adapter cable distance to connect MAUs. Use the following rules for Token-Ring cabling: ■ Maximum number of nodes: 96 ■ Maximum number of MAUs: 12 ■ Maximum patch cable distance between a MAU and a node (not including 8-foot adapter cable): 150 feet ■ Maximum patch cable distance between two MAUs: 150 feet ■ Maximum patch cable distance connecting all MAUs: 400 feet ■ Connect nodes to the ports on the MAU labeled 1 to 8. ■ Connect all MAUs with patch cables using the ports labeled RI (Ring In) and RO (Ring Out). The RO port of the last MAU connects to the RI port of the first MAU, creating a ring. ■ Before connecting cables, initialize each port you will use by plugging in the Setup Aid and waiting for the click. Then remove the Setup Aid. ■ Avoid placing the cable on or near any electrical devices that could cause interference on the line (such as florescent lights or electric motors). ■ NetWare Lite only supports a total of 25 nodes on the entire network. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Optimizing a Server Hard drive DOCUMENT ID#: FYI.P.6014 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Optimizing a Server Hard drive During the day to day work on your computer, files are deleted, rewritten, or replaced on the hard disk. This will eventually cause your files to be "fragmented." Fragmented refers to a file being divided into pieces and those pieces being located throughout your hard disk instead of in one contiguous block of disk space. Thus, if you try to access one of these files, the hard disk has to look for a single file in several places. This in turn causes your hard disk to respond slowly. The more fragmented your disk is; the slower it will respond. If the hard disk is in a NetWare Lite server, the entire network can be affected. To eliminate this effect, consider "optimizing" you hard disk. A disk is optimized by rearranging the data so that files are not spread out over the disk. Many different utilities are available for optimizing hard disks. Please consider the following before optimizing your hard disk: ■ It is vital that no other stations access your hard disk while the utility is running. ■ Disk Optimizers can take a considerable amount of time to complete data arrangement (20 minutes or more). ■ It is recommended that you have a backup of your vital information before optimizing. ■ If your hard disk is in a NetWare Lite server, the optimizing utility must be executed from the server itself and not from a client. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing a Client DOCUMENT ID#: FYI.P.6019 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Installing a Client To install NetWare Lite and configure your computer as a client, do the following steps. Depending on your current setup, the installation program may skip some of the steps. 1. Insert the diskette labeled PROGRAM into the A: (or B:) drive. 2. Type A:INSTALL, and press <Enter>. 3. Verify that "Make this machine a client" is highlighted, and press <Enter>. 4. Type in the path of the directory where you want NetWare Lite installed, or simply press <Enter> to accept the default. You may include the A: or B: drive letter if your computer does not have a fixed disk installed. See Fax Document 230 or FYI.P.6017 for more information on installing to a floppy diskette. 5. Insert the diskette labeled DRIVER into the A: drive, and press <Esc>. 6. Use the arrow keys to highlight the type of network board in your machine, and press <Enter>. If you are not sure which board to choose, refer to the hardware documentation to determine what type of board you have or which interface it is compatible with. 7. A window showing default settings for your board is displayed. You may change these if necessary by highlighting the item and pressing <Enter>, then highlight the correct value and press <Enter>. Refer to the hardware documentation if you are not sure what the settings should be. When the settings are correct, press <Esc>. 8. Answer YES or NO to the "path" message. Note that if the C:\NWLITE directory is not in the DOS path, you will have to CD to it to use the NET utility. You will also have to include the path for every NET command executed at the command line. 9. Answer YES or NO to the "lastdrive" message. Note that LASTDRIVE should be set to the G: drive or higher to use the NET utility. If you answer NO, you must edit the CONFIG.SYS file to include a LASTDRIVE command and reboot before you can use any NET command. 10. NetWare Lite is now installed. Press <Esc> to exit the installation program. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing a Client and Server DOCUMENT ID#: FYI.P.6020 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Installing a Client and Server The computer you are installing NetWare Lite on must have a hard disk to be configured as a server. Do not simply copy the files off the original (or backup) diskettes. To install NetWare Lite and configure the computer as both server and client, perform the following steps. Depending on your current setup, the installation program may skip some of the steps. 1. Insert the diskette labeled PROGRAM into the A: (or B:) drive. 2. Type A:INSTALL, and press <Enter>. 3. Use the arrow keys to highlight "Make this machine a client and a server," and press <Enter>. 4. Type in a name for the server, and press <Enter>. 5. FILES must be set in the CONFIG.SYS file for the server to run. The default value shown should work in most situations. If you know that you need to use different value, answer NO to the "files" message and edit CONFIG.SYS appropriately. 6. BUFFERS must be set in the CONFIG.SYS file for the server to run. The default value shown should work in most situations. If you know that you need to use a different value, answer NO to the "buffers" message and edit CONFIG.SYS appropriately. 7. Insert the diskette labeled DRIVER into the A: drive, and press <Esc>. 8. Use the arrow keys to highlight the type of network board in your machine, and press <Enter>. If you are not sure which board to choose, refer to the hardware documentation to determine what type of board you have or which interface it is compatible with. 9. A window showing default settings for your board is displayed. You may change these if necessary by highlighting the item and pressing <Enter>, then highlight the correct value, and press <Enter>. Refer to the hardware documentation if you are not sure what the settings should be. When the settings are correct, press <Esc>. 10. Answer YES or NO to the "path" message. Note that if the C:\NWLITE directory is not in the DOS path, you will have to CD to it to use the NET utility. You will also have to include the path for every NET command executed at the command line. 11. Answer YES or NO to the "lastdrive" message. Note that LASTDRIVE should be set to the G: drive or higher to use the NET utility. If you answer NO, you must edit the CONFIG.SYS file to include a LASTDRIVE command and reboot before you can use any net command. 12. NetWare Lite is now installed. Press <Esc> to exit the installation program. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing a Server DOCUMENT ID#: FYI.P.6021 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Installing a Server The computer you are installing NetWare Lite on must have a hard disk to be configured as a server. Do not simply copy the files off the original (or backup) diskettes. To install NetWare Lite and configure the computer as a server, do the following steps. Depending on your current setup, the installation program may skip some of the steps. 1. Insert the diskette labeled "program" into the A: (or B:) drive. 2. Type A:INSTALL, and press <Enter>. 3. Use the arrow keys to highlight "Make this machine a server," and press <Enter>. 4. Type in a name for the server, and press <Enter>. 5. Insert the diskette labeled DRIVER into the A: drive, and press <Esc>. 6. Use the arrow keys to highlight the type of network board in your machine, and press <Enter>. If you are not sure which board to choose, refer to the hardware documentation to determine what type of board you have or which interface it is compatible with. 7. A window showing default settings for your board is displayed. You may change these if necessary by highlighting the item and pressing <Enter>, then highlight the correct value, and press <Enter>. Refer to the hardware documentation if you are not sure what the settings should be. When the settings are correct, press <Esc>. 8. Answer YES or NO to the "path" message. 9. FILES must be set in the CONFIG.SYS file for the server to run. The default value shown should work in most situations. If you know that you need to use a different value, answer NO to the "files" message and edit CONFIG.SYS appropriately. 10. BUFFERS must be set in the CONFIG.SYS file for the server to run. The default value shown should work in most situations. If you know that you need to use a different value, answer NO to the "buffers" message and edit CONFIG.SYS appropriately. 11. NetWare Lite is now installed. Press <Esc> to exit the installation program. See FYI.P.6004 "SERVER Only Instead of SERVER and CLIENT" for more information on whether you should also install the client software. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Logging in After Installation DOCUMENT ID#: FYI.P.6022 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Logging in After Installation The first time you log in to a newly installed network, only one user, SUPERVISOR, will be defined on the network. To log in, type NET LOGIN SUPERVISOR or type NET and press <Enter> and type SUPERVISOR and press <Enter> when prompted for a username. If you are installing on a network where other servers are already running, the user accounts defined on the network will also be defined on servers you install. You will need to consult with the administrator of the network to find out what user accounts are defined and how you may log in to the network. Note: The SUPERVISOR account on a newly installed network has no password. For security reasons, Novell recommends that you set a password on the SUPERVISOR account soon after installation. Do not forget this password. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Shared Resources (Network Directories and Printers) DOCUMENT ID#: FYI.P.6023 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Shared Resources (Network Directories and Printers) Shared resources are those resources, network directories, and printers that are shared with clients on a network. Novell suggests that network directories and printers be given descriptive names. ■ Good names for network directories might be the following: TURBOC, WORDPERFECT, GAMES, IBM_DOS_310 or PUBLIC. ■ Good names for network printers might be the following: LASERJET_II, EPSON_DOT. Names that might not be good are CDRIVE, PRINTER1, PRINTER2. These names provide no indication of what applications or what types of printers are being made available. You will notice that during NetWare Lite installation, a CDRIVE network directory is created for you. When you become familiar with the product, give this resource a more descriptive name. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Make Shared Executables Read-Only DOCUMENT ID#: FYI.P.6024 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Make Shared Executables Read-Only Executable files that will be run by more than one user at a time need to be marked as read-only. If they are not, then you may notice, at times, that you are temporarily denied access to a file you wish to run. Example: You may get a message that access was denied or that the EXE file could not be run. If this happens, mark the executable files read-only using the DOS ATTRIB command. Type ATTRIB +R *.EXE in the directory where the executable files exist. This example marks the *.EXE files read-only. All shared .COM, .BAT, and .OVL files should be marked as well. The read-only attribute can be cleared using the same command replacing the +R with -R. (See DOS documentation for information on the ATTRIB command.) SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing Conventions and Suggestions DOCUMENT ID#: FYI.P.6025 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Printing Conventions and Suggestions Chances are you bought NetWare Lite to share one or more printers. For this reason, give special attention to the following remarks: Local Network Printers When a printer is assigned as a network printer, you should only access that printer through the network. You may have a printer attached to your workstation that has been defined as a Network Printer. In this case, you should capture a port when you wish to print to it. If you print to it directly (not using capture), you may cause print job corruption. Characters Per Second and Print Buffers Network printers are created in the NET menu utility in the "Supervise the Network" category. When a printer is created, you can configure the performance of the printer relative to the DOS running on the same machine where the printer is attached. This is done by modifying the "Chars per second" parameter with the "Print buffer size" parameter of the server configuration. The print buffer is an area in memory where characters are stored before being printed. The larger the print buffer size, the less often the server will need to go to disk to read more characters to print. If the "Chars per second" value is high (relatively speaking) and the "Print buffer size" is large (relatively speaking), the printer will be driven faster and the DOS running on that machine will be interrupted more often to send characters to the printer. The converse is also true if the value of "Chars per second" is low and "Print buffer size" is small. These values should also be tuned to the speed or desired speed of the printer. If the printer is physically a "slow" printer, then setting the "Chars per second" parameter to a high number will have no effect. Additionally, if the "Chars per second" is set higher than the "Print buffer size" parameter then this will have little effect, as well. Setup Strings One of the options available on network printers is setup strings. You can define up to ten setup strings for each network printer. In short, a setup string is a series of characters that put the printer into a particular mode (such as landscape mode or large characters mode). By default, the DEFAULT setup string is set to nothing. The DEFAULT setup string should be set to a sequence of values that reset the printer. Many printers use the string "1E 45" (<Esc>E) to reset the printer (Check the documentation for your printer to find out what sequence resets the printer). The manual that came with the printer should describe the values that place the printer into different modes. Setup strings are always entered using hexadecimal codes. By defining more than one setup string for a Network Printer, it is possible to submit jobs that will print in different printer modes. Setup strings can be used as part of the NET CAPTURE command or in the "Print" category of the NET menu utility. An example of its use with NET CAPTURE is provided below. Capture Settings The term "capturing ports" refers to redirecting print jobs from the normal printing device to someplace else; in this case, a network printer. To capture a port, you must first load CLIENT and log in to the network. You can then access network printers by capturing ports with the NET CAPTURE command. Several options that are available with this command are discussed in the manual, as well as in the on-line help in the NET menu utility, and at the command-line when NET CAPTURE HELP is typed. A sample command-line might look like the following: NET CAPTURE LPT1 LASERJET B=N D=Y S=LANDSCAPE This example specifies that all jobs sent to LPT1 of the local machine will be redirected to the network printer LASERJET. It also specifies that for all print jobs sent to LPT1 (LASERJET), NO banner should be printed and each job should start printing before the job has been completely submitted (direct printing). Finally, this job is printed using the LANDSCAPE setup string (created previously on printer LASERJET). The LANDSCAPE setup string values are sent to the printer just before the data of each print job sent to LPT1. The DEFAULT setup string values are sent to the printer after each print job is printed (thus resetting the printer for the next job sent to this printer). From the NET menu utility, it is also possible to submit a print job and have the job immediately go on hold. When a print job is on hold, it is placed on the queue but not printed. It can be taken off hold (and thus printed) by selecting the job from the print job list and changing the flags of the job. Capturing COM Ports The documentation incorrectly states that as a client, you can capture COM1 or COM2. The COM1 and COM2 ports can only be used by a server. A network printer can be assigned to the COM1 or COM2 port. Clients can then capture LPT1, LPT2, or LPT3 to a network printer that has been created and assigned to COM1 or COM2. Postscript Printing Because of the nature of postscript printers, special care must be taken when sending print jobs. You should make sure your capture has the following set: BANNER=No TABS=0 FORMFEED=No You may also want to set the WAIT parameter to a value higher than 10 seconds. If your print job gets split to multiple jobs when printing to a postscript printer, you will want to increase the WAIT value. Increase it until your print job comes out all in one job. Using WAIT=0 The WAIT=0 should only be used if the application you are using will close the print job. If the application does not close the print job, using WAIT=0 will keep the print job open until it is closed explicitly. A print job on LPT1 can be closed manually from the DOS command-line by sending a formfeed or <Ctrl>+L, displayed ^L (press and hold the <Ctrl> key while pressing the <L> key, then release the <L> key and <Ctrl> key). Type ECHO ^L > LPT1. This sends a form feed character to LPT1 and closes the job. Generally, using a WAIT value of 10 or so is adequate. CAUTION: If you use WAIT=0 and DIRECT=Y, you will hold the printer until the print job is explicitly closed. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite Prerelease White Paper DOCUMENT ID#: FYI.P.6026 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NetWare Lite Prerelease White Paper Overview NetWare Lite(tm) is Novell's new peer-to-peer operating system. Its client/server architecture provides networking features for small LANs. NetWare Lite is designed to be easy to install and use. It supports disk and printer sharing for up to 25 nodes on a single physical LAN segment. Each node in the network can be configured as either a client, a server, or both. Both client and server are DOS terminate-and-stay-resident (TSR) programs. Therefore, the server operates in a nondedicated mode with DOS as the underlying operating system. Program Details NetWare Lite consists of three TSR software pieces and a single utility. The client supports the Microsoft interrupt 2fh redirector interface and occupies approximately 12 KB of workstation memory. The server is another DOS TSR that uses DOS networking server hooks. The average configuration requires 45 KB of workstation memory. The server runs in real mode on an IBM PC, XT, AT or compatible computer with a hard disk. The server uses DOS and the DOS file system to share files with network clients. Both programs use Novell's IPX protocol. IPX is provided by a trio of TSRs that implement Novell's ODI protocol interface and MLID LAN board interface. The group of programs providing the IPX protocol requires approximately 15 KB of workstation memory depending on the LAN driver used. NetWare Lite provides a group of Multiple Link Interface Drivers (MLID) drivers with the product to support a large number of LAN boards. NetWare Lite also runs with other LAN boards if an MLID compliant driver is provided. NetWare Lite also runs over the older "linked" version of IPX if it is already present. Network operations and administration are performed using a single utility that functions in either command-line or menu-driven mode. The utility incorporates extensive online user help. The client and server communicate using a request/response protocol similar to that used by the dedicated NetWare operating system. The server can support up to 25 simultaneous client connections. All nodes on a NetWare Lite network, both clients and servers, exist on a single physical LAN segment or on LAN segments connected through Media Access Control (MAC) layer bridges. The underlying operating system for the server and client is DOS version 3.x (3.1 and above), 4.x, 5.0, or DR DOS 6.0. Disk redirection, file attributes, and file sharing are supported including enforcement of DOS sharing modes and record locking through DOS' SHARE.EXE. Printer redirection is supported through both DOS device I/O and BIOS printer services. Network Features The server provides network directories that can be shared by a client as a redirected disk. A network directory associates a logical name to a subdirectory on a physical drive at the server. More than one network directory can be defined within the same subdirectory tree on a server's physical disk. Both hard drives and floppy drives can be shared as network directories. The server can also provide network printers that can be shared by a client as a redirected printer port. A network printer associates a logical name to a printer attached to the server. Network security is enforced through user accounts. Access to network resources can be controlled on a per-user basis using a simplified rights scheme implemented through access control lists. A user's identity is verified using password authentication. Passwords are encrypted both in the user database and during transmission on the network. A full range of user account restrictions and password requirements is enforced by the operating system. Network directories can be manipulated dynamically. For instance, a new network directory can be created and used without rebooting the server on which it exists. Print jobs are spooled and can be manipulated (held, deleted, or other) while in the print queue at the server. The server supports both parallel and serial print devices and can spool simultaneously to multiple printers. Print jobs can be controlled by a variety of printing options such as the following: ■ printing a banner ■ number of copies ■ tab expansion ■ printer setup strings ■ holding a job Also supported is direct printing whereby a job can begin despooling (printing) before it has finished being submitted to the print queue. A variety of statistics is reported for servers that can be monitored and used to reconfigure a server for enhanced memory utilization or performance. The network maintains an audit log so that activities on the network can be tracked. An error log is also kept to aid in isolating and resolving problems with the network. The installation program includes verification that LAN boards, cables, and IPX software are installed correctly and are operational. Additional miscellaneous features include the following: ■ Messages can be sent to other users' video displays. ■ It is possible to disable the reception and display of messages on your terminal. ■ Time for all or part of the machines on the network can be synchronized. ■ The server has a pop-up window that displays printer errors and necessary operator actions and another window that requests confirmation when the user reboots the machine. Operational Details (Advanced Features) NetWare Lite's implementation of advanced networking techniques achieves simplicity of operation as well as network performance and robustness. Shared directories and printers and users are presented in a network-wide view. Network directories and printers can be used without reference to (or user's awareness of) the location of their physical component. Furthermore, client access to a resource is unaffected by moving the resource from one server to another. Although resources are presented to the user in a conglomerate view, servers operate independently of each other. Also, a single server or group of servers can go down without disrupting the rest of the network. The user database is a distributed, replicated database. Therefore, user accounts are administered on a network-wide rather than on a per-server basis. A user logs into the network rather than into specific servers. The password is required only once (the client software, not the user, handles authentication with new servers as their resources are used). Only one account exists on the network for each user. This greatly simplifies user administration. If user accounts are administered when a portion of the network is down, the user database is resynchronized when that portion again becomes operational. Because the database is distributed, network operation continues even if only one server is functional. The client can reconnect (transparently to the user) with a server and continue most operations even after a server has gone down and is brought back up. In such a case, drives do not need to be remapped nor must printer ports be recaptured. However, information for open DOS files cannot be retained through a server reboot. NetWare Lite supports decentralized network administration. Network resources and server configurations can be manipulated from any machine (running the client software) on the network. Remote administration of servers can be optionally disallowed per server. The server implements a read-ahead cache for enhanced performance. NetWare Lite is also compatible with third-party DOS-based disk caches. Several third-party caches have been tested and found to enhance network performance by the same amount that they enhance local DOS disk performance. NetWare Compatibility NetWare Lite is compatible with NetWare. NetWare Lite software (both client and server) can use either the ODI implementation of IPX or the original linked implementation of IPX. The client and server both coexist with the NetWare DOS shell. Thus, a client may have drives mapped to volumes on dedicated NetWare 286 or 386 servers while simultaneously having other drives mapped to NetWare Lite network directories. Also, dedicated NetWare volumes can be chained into a NetWare Lite network by mapping a drive to the volume using the shell and then providing a network directory, based on that drive, to Lite clients through the nondedicated NetWare Lite server. The same holds true for simultaneous port captures and chained printer ports. Applications Compatibility NetWare Lite is compatible with application software that uses single-machine DOS calls. Also, NetWare Lite supports network applications that use only DOS networking APIs. This includes all DOS networking APIs. The NetWare application programming interface is not supported. Peer-to-peer network level APIs are also supported. This includes IPX, SPX, and NetBIOS. To use the NetBIOS API with NetWare Lite, you must load Novell's NetBIOS emulator software (available separately). SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Location Independence DOCUMENT ID#: FYP.P.6027 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Location Independence You will notice that NetWare Lite resources are location independent. Suppose you create a network directory named ALL_APPS on a server named DEPT_SERVER. Server DEPT_SERVER is a 8 MHz 286 machine with a 40 MB hard disk. All clients map drives to ALL_APPS and use it every day. Now suppose you buy a 50 MHz 486 machine with a 1 GB disk drive on it. You want to move the network directory ALL_APPS to this new machine. You install this new machine, and call it HOT_SERVER. You can then create a new network directory on this new server and call it ALL_APPS (same name as before). You then copy the files from DEPT_SERVER to HOT_SERVER. ALL_APPS can now be removed from DEPT_SERVER. All your clients will now use ALL_APPS from HOT_SERVER and nothing need be changed from the client's perspective. The clients do not need to know that the location of the network directory ALL_APPS has moved. This same principle applies to network printers SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Auxiliary NetWare Lite Files DOCUMENT ID#: FYI.P.6028 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Auxiliary NetWare Lite Files Included with NetWare Lite are four extra programs that are not documented. These files are not needed for NetWare Lite to run but add fun and functionality. They are: DEDICATE.COM, DEMO.EXE, NETBIOS.EXE, and NLSNIPES.EXE. DEDICATE.COM -- DEDICATE is a little program that can be run on a server to improve performance. It is a useful program to be run on NetWare Lite machines that are acting as dedicated servers or if a machine is a server/client and the client is not going to be active for a while. To run DEDICATE, type DEDICATE when in the C:\NWLITE subdirectory on the machine running SERVER.EXE. DEMO.EXE -- DEMO is a networking demonstration program that shows how workstations can communicate using shared file access. When run, a worm is shown moving around on the screens of the workstations running DEMO.EXE. As the worm covers each screen, eventually the word "LITE" is shown. To run DEMO, change to the same directory on the same server on each machine that will be running DEMO. With DEMO.EXE in your PATH, type DEMO and press <Enter> on each workstation. DEMO works best if run in a Left-to-Right fashion. That is, starting on the leftmost workstation, run DEMO.EXE and move right running DEMO on each machine. The screens are connected, starting left and moving right, in the order that DEMO was started. Once running, you can drive your worm using the arrow key. DEMO will only support nine workstations running simultaneously. NETBIOS.EXE -- This is the NetBIOS that is included with regular NetWare. It can be loaded any time after IPXODI is loaded. Some applications require the presence of NetBIOS. For this reason, NetBIOS is provided with NetWare Lite. For more documentation on NETBIOS.EXE, contact the nearest Novell Authorized Reseller. NLSNIPES.EXE -- NLSNIPES is a game. One to five users can play at a time. Everyone who wants to play NLSNIPES must map a drive to the same Network directory on the same server. To run, type NLSNIPES. You will then be asked for two initials; this uniquely identifies your "man" as you play. The first person to run NLSNIPES is the "starter." As people run NLSNIPES and enter their initials, they will see the initials of the other players that are entering the game. Once the desired group is ready, the "starter" will press <Enter> to begin. Move your "man" through the maze killing snipes, generators, and other "men." For instructions on how to move and shoot, type "NLSNIPES /H" at the command-line. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Workstation Time DOCUMENT ID#: FYI.P.6029 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Workstation Time To keep the system time of network clients synchronized, Novell suggests that "NET TIME <server_name>" be placed in everyone's AUTOEXEC.BAT or STARTNET.BAT file. <Server_name> should be a machine that keeps fairly accurate time. This becomes especially important if NetWare Lite is being used in a software development environment where MAKE.EXE is being used. MAKE.EXE requires strict time synchronization. If NET TIME is used, then MAKE.EXE will function smoothly. Furthermore, the time on all servers can be synchronized by using the "Time Synchronization" option in the "Supervise the Network" menu. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Loading IPXODI A DOCUMENT ID#: FYI.P.6030 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Loading IPXODI A In the STARTNET.BAT file that is created for you, the line "IPXODI A" appears. The parameter "A" instructs IPXODI to only load IPX that makes it so IPXODI uses less memory. If you have an application that needs SPX to run, remove the "A" from this line when loading IPXODI then SPX will also be loaded. You can type "IPXODI ?" to see a list of all available options for IPXODI. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Compatibility with the NetWare Shell DOCUMENT ID#: FYI.P.6031 DATE: 01DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Compatibility with the NetWare Shell If your site is currently using Novell NetWare and you are installing NetWare Lite on the same LAN, then there are some guidelines that should be followed for both to function properly. NetWare Lite functions on a single LAN segment. In other words, NetWare Lite packets do not cross Novell bridges (NetWare Lite packets do cross MAC layer bridges or repeaters, however). In a site that has existing NetWare, each NetWare Lite network will be constrained to a single LAN segment. If there are workstations that will load both the NetWare shell and NetWare Lite software, Novell strongly suggests the following load order: IPX (The IPX you had or IPXODI that came with NetWare Lite; either one but not both) DOS Share (SHARE.EXE, if becoming a SERVER) NetWare Lite Server (SERVER.EXE, if desired) NetWare Lite Client (CLIENT.EXE, if desired) NetWare Shell (NETx.COM) After you have installed the Client to a workstation that will also be running the NetWare Shell, you will need to modify your AUTOEXEC.BAT or appropriate batch file to load the files in the correct order. Note: With LASTDRIVE set, the NetWare Shell will map the first drive past LASTDRIVE to the SYS:LOGIN directory of the NetWare server for you to log in. If LASTDRIVE is not set, DOS defaults it to the E: drive; thus, F: would be mapped to SYS:LOGIN. Also, if you use the MAP *1:= command in your login script, *1 means the first drive past LASTDRIVE. If you are dependent on certain drives being mapped with certain letters, changing LASTDRIVE may change which drive letters are mapped. Be aware that all drive letters, A: through Z:, can be mapped to NetWare servers. (NetWare Lite can only map A: through LASTDRIVE.) SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Disabling the Server DOCUMENT ID#: FYI.P.6032 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Disabling the Server There is no way to remove the server or client from memory once either is loaded. The server can be disabled after loading by doing the following: 1. Press <Ctrl>+<Alt>+<Del> as if you were rebooting. 2. When the reboot window comes up, press <1> to disable the server. This simply turns the functionality of the server off; however, it is not removed from memory. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Improving Server Performance DOCUMENT ID#: FYI.P.6033 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Improving Server Performance Fragmented files on the hard disk drive of a server can adversely affect performance. It is suggested that you periodically unfragment the files on the hard disk drive of each server. This can be done using any of a number of disk optimizing or disk compression tools available in the market place. ***** WARNING ***** Make sure the server is not running when this type of operation is done! Never run any low-level disk repair utilities on the hard disk drive of the server while the SERVER is loaded. This can cause corruption of data stored on the hard disk drive. This includes CHKDSK /F, disk-doctor utilities, and disk-optimizing utilities. Low-level utilities can only be run directly on the server machine. You cannot run them from clients that have a drive mapped to the server. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Renaming Servers and Reconnection DOCUMENT ID#: FYI.P.6034 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Renaming Servers and Reconnection Whenever a server is renamed, you should reboot that server soon and have the clients that were connected to that server, relogin. Clients cannot reconnect to a server that was renamed. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Server Optimization and Functions DOCUMENT ID#: FYI.P.6037 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Server Optimization and Functions Disk Caches NetWare Lite does not ship with a disk cache. Novell has tested with several (read many) commercially available disk cache products and found them to be quite inexpensive while adding significant performance to the NetWare Lite server software. For higher performance of the NetWare Lite server, Novell suggests that you acquire a disk cache and install it on the server machines. Some cache tuning may be necessary for best results. Server Configuration For best performance, Novell suggests that you increase receive buffer and read buffer sizes to what is supported by the network topology (such as Ethernet, Token-Ring) up to a maximum of 4096 bytes using a multiple of 512 bytes. In fact, if 4096 is selected then the server will truncate the value to the maximum value supported by the topology. This tuning allows clients to request more data from (or send more data to) the server with each read (write) operation. When more data is sent, fewer requests are necessary and better performance is obtained. This enhancement does increase the size of server when it is resident in DOS. Depending on the load being placed on the server, it may be beneficial to increase the number of receive buffers and read buffers. In general, Novell found that 8 to 12 receive buffers are enough for even the most heavily loaded server. Similarly, 5 to 10 read buffers are sufficient. These values do not need to be more than one or two above the number of simultaneous connections (up to the suggested maximums of 8 to 12 receive buffers and 5 to 10 read buffers). Mapping verses SUBSTing If your machine is a server and you would like to map to the server, it is recommended that you SUBST to the server instead of mapping to server. SUBST is a DOS command that lets you assign a drive letter to a directory on another drive. Example: If you usually map to the server with the G: drive to the Network Directory APPS and APPS is actually the C:\APPS directory, the NET MAP G: APPS command could be replaced by SUBST G: C:\APPS command. To remove this substitution, you would type SUBST G: /D. Using this substitution rather than a mapping will result in better performance for operations done on the G: drive. Mapping Local Drive You can map drives that are local (A: or B:) and use them temporarily as network drives. However, as a general practice, it is not recommended. If you run out of drive letters to map, increase LASTDRIVE in your CONFIG.SYS. Use of ASSIGN Do not use ASSIGN with NetWare Lite. The DOS reference manual (3.3) recommends that you use SUBST instead of ASSIGN and explains how to do so. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Double Drive Mappings DOCUMENT ID#: FYI.P.6039 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Double Drive Mappings If you are using NetWare Lite on the same network with Native NetWare (NetWare v3.11 or v2.2) you may run across the situation where NetWare Lite's Net utility reports a single drive letter mapped to two different directories simultaneously (such as two F: drives). These "double drive mappings" will occur in the following scenario: Map a drive letter with NetWare Lite (NET MAP F: CDRIVE SERVER1). Log in to a NetWare v3.11 or v2.2 server. If your server's system login script has a drive mapping that uses the same drive letter (F:) as the pervious NetWare Lite mapping it will override the mapping without giving the usual NetWare warning "drive already in use by local drive." Note: You will get the warning if you map from the command line. If you then return to NetWare Lite's Net utility and select drive mappings, you will see that the F: drive appears as a NetWare Lite drive mapping and as a Native NetWare Mapping. When this situation occurs, the mapping to Native NetWare will be the active mapping. NetWare Lite will flag its own mapping inactive and is, therefore, inaccessible to the user. The NetWare Lite mapping can not be deleted as long as it is inactive. To make the NetWare Lite mapping active, delete the Native NetWare mapping. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DOS Error Codes and Extended Error Codes DOCUMENT ID#: FYI.P.6069 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM DOS Error Codes and Extended Error Codes The following is a list of generic error codes and extended error codes returned by DOS. Note: Different versions of DOS may return different error codes. DOS Error Codes 1 Invalid function number 2 File not found 3 Path not found 4 Too many open files 5 Access denied 6 Invalid handle 7 Memory control blocks destroyed 8 Insufficient memory 9 Invalid memory block address 10 Invalid environment 11 Invalid format 12 Invalid access code 13 Invalid data 14 Reserved 15 Invalid drive was specified 16 Attempt to remove the current directory 17 Not same device 18 No more files 19 Attempt to write on write-protected disk 20 Unknown unit 21 Drive not ready 22 Unknown command 23 Data error (CRC) 24 Bad request structure length 25 Seek error 26 Unknown media type 27 Sector not found 28 Printer out of paper 29 Write fault 30 Read fault 31 General failure 32 Sharing violation 33 Lock violation 34 Invalid disk change 35 FCB unavailable 36 Sharing buffer overflow 37-49 Reserved Extended Error Codes 50 Network request not supported 51 Remote computer not listening 52 Duplicate name on network 53 Network name not found 54 Network busy 55 Network device no longer exists 56 Net BIOS command limit exceeded 57 Network adapter hardware error 58 Incorrect response from network 59 Unexpected network error 60 Incompatible remote adapter 61 Print queue full 62 Not enough space for print file 63 Print file was deleted 64 Network name was deleted 65 Access denied 66 Network device type incorrect 67 Network name not found 68 Network name limit exceeded 69 Net BIOS session limit reached 70 Temporarily paused 71 Network request not accepted 72 Print of disk redirection is paused 73-79 Reserved 80 File exists 81 Reserved 82 Cannot make directory entry 83 Fail no INT 24 84 Too many redirections 85 Duplicate redirection 86 Invalid password 87 Invalid parameter 88 Network data fault SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Testing the DOS Errorlevel DOCUMENT ID#: FYI.P.6071 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Testing the DOS Errorlevel Programs can set a flag in the DOS environment called errorlevel. This is usually used by the program to pass information to DOS, such as returning a pass or fail status of the particular program. This flag can be tested at the DOS level in the following format: IF not ERRORLEVEL x command ■ The "not" is optional. ■ The "x" is the number to be tested. ■ The "command" is the command to be issued if this test passes. Note: The purpose of this document is to give general information on how to use it with NetWare Lite and not to explain all the functionality of the DOS ERRORLEVEL flag. For further information, please consult your DOS documentation. NetWare Lite v1.1 has the undocumented feature of setting the errorlevel flag. The NET command line utilities will set it according to the status of the command. Errorlevel is set to non-zero if the command fails or does not complete properly. Example: If the command NET LOGIN TOMMYJO was issued and the user TOMMYJO failed to log in for whatever reason (entered an invalid password, no servers were found), the DOS errorlevel would be set to non-zero. If TOMMYJO was logged in properly, the errorlevel would be set to zero. The following batch file demonstrates use of this command. The batch file will attempt to log in user MURCHMAN to the network. If MURCHMAN is successfully logged in, the batch file will test to see if the server MAHONEY is on the network. If it is, the LPT1 port will be captured to the network printer LASER on server MAHONEY. Upon failing any of the above conditions, error messages will be displayed to the user. Only after everything has been completed will the PROGRAM application be executed. :LOGIN NET LOGIN MURCHMAN IF ERRORLEVEL 1 GOTO LOGINERR :CAPTURE NET SLIST MAHONEY IF ERRORLEVEL 1 GOTO SLISTERR NET CAPTURE LPT1 LASER MAHONEY ECHO You are logged in to NetWare Lite and port LPT1 has been ECHO captured to printer LASER. PAUSE GOTO DONE :LOGINERR ECHO. ECHO You were not correctly logged into the NetWare Lite. This ECHO program will not continue until you are correctly logged in. GOTO LOGIN :SLISTERR ECHO Server MAHONEY is not currently on the network. PAUSE :DONE CLS PROGRAM Note: The errorlevel flag is always tested at 1. Because of the way DOS evaluates the errorlevel, all non-zero values will pass on a test of 1. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite and Windows 3.1 (Possible Solutions) DOCUMENT ID#: FYI.P.6095 DATE: 06JAN93 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM Windows 3.1 may exhibit one or more of the following problems: ■ On a Server-Client that is running Windows and attempts to print, print jobs will not start printing until Windows is exited. ■ On a Server-Client that is running Windows, other stations will appear to lockup (hang) until Windows is exited on the Server-Client that is running Windows. ISSUE/PROBLEM The symptoms seem to be caused due to a configuration issue. Novell currently does not know the exact cause of the problem; although, it appears that some non-Microsoft Windows (and possibly non-Windows) applications may be doing something that Microsoft applications do not do such as causing SERVER.EXE to not get any CPU cycles thus displaying the above symptoms. SOLUTION 1) Make sure that the Exclusive in Foreground box is not selected in the 386 enhanced ICON in the control panel. 2) Remove any references to programs in the LOAD/RUN line in the WIN.INI file. 3) Remove any programs that are in the StartUp group that run when Windows is started. Note: The above information may or may not work in each case. Novell currently has a field test patch for this issue. Please call Technical Support and register a call to determine if the patch applies to your situation. If so, a copy of the patch will be made available to you. This field test patch will be generally available when the patch has passed field testing. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: How To Configure a NetWare Lite Server DOCUMENT ID#: FYI.P.6060 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM How to Configure a NetWare Lite Server The purpose of this document is to explain the server statistics that are configurable within NetWare Lite. These Server statistics can be viewed and changed in the Net utility. To access the configuration menus, do the following steps: From the c:> prompt, type NET Select "Supervise the Network" Select "Server Configuration" to change settings. Select "Server Status" to view settings. SERVER CONFIGURATION SCREEN The following is an example of the server configuration screen with default settings: Configuration Information for Server NetWare Lite CFG FUTURE Connections (2-25) 4 4 Client tasks (4-200) 10 10 Network directories (2-20) 4 4 Network printers (0-5) 1 1 Print buffer size (256-4096) 512 512 Number of receive buffers (3-20) 6 6 Receive buffer size (512-4096) 1024 1024 Number of read buffers (2-20) 3 3 Read buffer size (512-4096) 1024 1024 Allow remote management (Y/N) Y Y Future server name: NWLIT E CFG and FUTURE Columns There are two columns of statistics on the right side of this table labeled CFG and FUTURE. The CFG column indicates the settings that are currently being used. The FUTURE column is used to determine the network settings to be implemented the next time the network is started. If you want to make a change, make it in the FUTURE column and then reboot the machine. After the machine is rebooted, the new settings will be in effect and will appear in the CFG column. Configuration Settings Each item in the menu will be discussed in some detail. After each item is described, configuration information will be given to help correctly configure each item. CONNECTIONS Every computer on the network (client or server or both) has a connection table. This table keeps track of the number of connections that the computer has with other computers. This table is not able to be viewed by a user; however, the number of connections can be limited on a server. A connection is established when one computer accesses another computer across the network. For example, a connection is established if a client accesses a network resource, such as a network directory or network printer, located on a server. Server Connection Table A server's connection table contains a list of the node addresses of every client computer accessing printers or network directories on that server. Because the connection is actually the node address of the network board, only one connection is established per machine, regardless of how many drives a computer has mapped or how many printers a client machine is captured to. It is not possible for the number of connections in the server connection table to be greater than the total number of clients on the network. For example, when a server receives a request to map a drive, it will look down the list of existing connections and will create a new connection only if the address of the requesting computer is not already on the list. Temporary Connections Temporary connections are occasionally established by the NET utility to do functions such as modifying a user account, changing a server's configuration. After the net utility has finished using the temporary connection, the connection is cancelled. Setting Connections Set the number of connections for each server by considering how many clients might be mapped or captured to the server at one time. Add one to that number to provide for any temporary connections. Each connection in the Server's configuration menu uses approximately 80 bytes of memory. CLIENT TASKS Client tasks are the number of programs permitted to open files on a server. Each time a program on a client uses a resource on a server (such as starting a program) one client's task is registered in a table on the server. This is the case whether the client loads the program from the server or whether it loads it from its own hard drive. If the same program opens more than one file, only one client task is still registered because the client tasks refer to the number of programs that are opening files and not the number of files that are open on the server. On the other hand, if two different programs on a client open files on a server, then two client tasks are recorded in the table. Some programs call other programs that use server resources. When this happens, client tasks will increase by more than one when the program is initially started. A variety of problems are associated with not having enough client tasks. Usually errors will be displayed by the application that is currently running. Occasionally, the whole network will hang. Client Task Configuration Information The number of client tasks defaults to 10. A good rule of thumb is to set the number of client tasks to 10 per machine connected to the server (For example, If five machines have drives mapped to a server, set the client tasks on the server to 50). This should provide enough client tasks to operate the network. Approximately 100 bytes of memory are reserved on a server per each client task. Check the server status screen frequently to verify that you have enough client tasks. If you see the PEAK number of tasks in the server status screen approaching the CFG number (within 6), you should increase the number of client tasks to avoid problems. The CFG number should always be at least six higher than the PEAK number. Proper configuration of the number of client tasks on a server is especially important under the following conditions: ■ When running Microsoft Windows ■ When using a disk intensive program (such as a database program) ■ When supporting many clients Network Directories A network directory is a directory on a server that can be accessed by clients on the network. Increasing the number of network directories on a server simply allows more of its directories to be accessed by users across the network. Network Directory Configuration Information Set the number of network directories to as many as needed (up to 20). Network Printers This figure designates the maximum number of network printers allowed on a server. NetWare Lite will support up to three printers per server. A printer on a server does not necessarily have to be designated as a network resource. It can be run locally if SERVER.EXE is not loaded into memory. Each network printer defined takes up approximately 884 bytes of memory on the server. Network Printer Configuration This number should correspond to the number of printers physically connected to the server and defined as network resources. The maximum number of network printers per server is three. PRINT BUFFER Print Buffer Size NetWare Lite uses a print buffer to temporarily store information before it is printed. A print job follows the following path to the printer: Application -- DOS -- Client -- || network ||-- Server -- Printer When someone prints a job from a client machine to a network printer, the information first goes to DOS. After interpreting that the printer port (LPT1 for example) has been captured to a network printer, DOS sends the print job to the network software on the client machine. The print job is sent across the network cabling to the computer with the printer attached and then taken by the server software and spooled to a directory on the hard drive. The path to where the data is being spooled is C:\NWLITE\NLCNTL \SLPT1. The NLCNTL subdirectory is a hidden directory and the SLPT1 directory corresponds to the printer port captured on LPT1. (If LPT2 was captured, the last subdirectory would be \SLPT2.) The job is spooled as a file then loaded to an area in memory called the print buffer. From the print buffer, the print job is sent to the printer. The print buffer speeds up the printing because accessing memory is much faster than accessing a hard disk drive. A large print buffer accesses information from the relatively slow hard drive fewer times and causes faster printing. Print Buffer Configuration Set the print buffer size to the maximum allowed value unless limited memory is available. RECEIVE BUFFERS Number of Receive Buffers Each NetWare Lite server has two types of buffers related to overall network communication that can be configured by a supervisor. They are the receive and read buffers. Understanding receive and read buffers and how to configure them requires an understanding of some basic NetWare Lite network communication concepts. When an application makes a request of DOS, such as reading data from a file or writing data to a file, DOS determines whether it can handle the request itself. If the requested operation involves a network resource, such as listing a network directory, DOS passes the request to the network that fills the request and gives the response back to DOS. Then, DOS passes the response back to the application. Each network request passes through four different stages before being sent out on the network cabling. The network provides information to DOS (such as which drives are actually network drives) so that DOS interprets when to pass requests to the network and when to return errors to the requesting application. Three programs provide the interface to the network hardware. They are the Internetwork Packet Exchange Protocol (IPX) driver (IPXODI.COM), the Link Support Layer (LSL) driver (LSL.COM), and the network-board driver (such as NE2000.COM). These three programs take requests from the network level and transform them into packets that are then sent out on the cable. When a packet is received at the server, SERVER.EXE is notified and the packet is placed in a free receive buffer. The server processes the request and does one of two things. If the requested operation is a disk read, the server reads the requested amount of data and places the response in a free read buffer. If the request is for anything else, the server places the response back in the receive buffer where it received the request. The data is then transferred back across the network to the application that originally made the request. Number of Receive Buffers Configuration Information Set the number of receive buffers to three more than the number of clients that will be simultaneously accessing the server. The extra receive buffers are important. The server may be servicing requests from every client on the network and still needs extra buffers to respond to additional incoming requests. Even though all client machines may have requests pending at the server, a client may resend a request and the server needs extra buffers to handle any extra packets from the clients. Receive Buffer Size Description and Configuration Information The network is limited to the type of network hardware that is being used. A receive buffer cannot be set to anything larger than the packet size of a particular type of board. Typically, Ethernet is limited to a packet size of 1450 bytes, and ARCnet and Token-Ring are capable of sending and receiving 4096 byte packets, which is the NetWare Lite limit. DOS reads information best in 512 byte increments, so receive buffers should be set to a multiple of 512 bytes even if the packet size is larger than the 512 byte multiple. For example, when using Ethernet boards, set the buffer size to 1024 bytes rather than the maximum allowed 1450 bytes. Because 1024 is an increment of 512, the 1024 setting will be faster than 1450 bytes. If you have a read buffer on one machine set to 512 bytes and the receive buffer on another machine set to 1024 bytes, the packets will be sent in 512 byte blocks rather than 1024 byte blocks. The receive buffers should be the same size as the read buffers on all machines in the network. READ BUFFERS Number of Read Buffers After information is read, it is placed in a read buffer to wait until the network is ready to send the information back to the requesting client. Each client machine can only reserve one read buffer on the server. Number of Read Buffers Configuration Information Set the number of read buffers to the number of clients that will be simultaneously accessing the server. One read buffer per client. More than one per client will only waste memory because a client can use only one read buffer. Read Buffer Size and Configuration Information Read buffers are very similar to receive buffers. The purpose is slightly different as is explained above, but the guideline for setting the read buffer size is the same as the guideline for setting the receive buffer size. Set the read buffer size the same as the receive buffer size. REMOTE MANAGEMENT Allow Remote Management If remote management is enabled, a network supervisor will be able to change a server's configuration settings from any machine on the network. If remote management is disabled, a server's configuration settings will only be able to be modified at the keyboard of the server itself. Note: Remote Management does not refer to modem use. Remote Management Configuration Enable or disable remote management depending upon the conditions in which the network is running. If security is a concern, remote management may need to be disabled. FUTURE SERVER NAME Future Server Name The future server name is the name that the server will be called the next time the network is started. SERVER STATUS SCREEN Status Information for Server NetWare Lite Server up-time Days Hours Minutes Seconds Server version CFG PEAK CURR Server address Connections Network Auditing Client tasks SHARE running Open files Server memory size Num net directories CUM Num net printers Server-busy packets Print buffer size Server cache hits Receive buffers Packets Received Receive buffer size Bad packets received Read buffers Watchdog terminations Read buffer size The Server status screen is a diagnostic tool that can be used to troubleshoot problems within the network and to optimize the speed at which the network runs. All the items listed on this screen are configured in other places; this screen only indicates what the current settings are. The Server status screen has some distinguishing features. The right hand column contains the statistics set in the Server configuration menu. These statistics are listed in three columns. The CFG column shows how the items are currently configured. The PEAK column shows how close to the configured setting each item has gotten since the network was started. The CURR setting shows the status of each item. The PEAK and CURR numbers are dynamic, meaning any changes will immediately show on the screen. The left hand column contains information that is set when the machine is started and has cumulative information that keeps track of the total performance of the network since the network was started. Server Up-Time This indicates how long the server has been running continuously since the network was loaded. Every time the network is restarted, the Server up-time figure is reset to zero. Server Version This displays the version of NetWare Lite that is currently running. The current version of NetWare Lite available is v1.0. Server Address The server address is the node address of the network board that is installed in the server. The node address is a unique number assigned to the network board that distinguishes it from other boards on the network. This number may be set with software settings or switches on the board, or it may be built into the board. Network Auditing Network auditing has a "yes" or "no" indicator displaying whether the auditing feature has been enabled. The audit log lists activities such as logins, logouts, and backup of network management files. The date and username associated with each activity appear in the log. Network auditing can be turned on and off within the NET utility in the "Supervise the Network" option. SHARE Running This screen lets you know whether SHARE.EXE has been loaded. SHARE is the DOS file used to control file locking and file sharing. SHARE is a necessary program to load when using a peer-to-peer network because it enables programs to be run concurrently and ensures proper file locking so two people do not access the same data file at the same time. Server Memory Size If this percentage is low, an increase of the number of read buffers may speed up your system. Server-Busy Packets This statistic informs the user of the number of times that a client resends a request to a server when the server was too busy to handle the request. A large number of server-busy packets (more than 1 percent) usually indicates that the server is not fast enough to handle the volume of requests that are being made. A third-party disk caching program will improve the speed of the server and will reduce the number of server-busy packets. Another event that will cause the server-busy packets to increase at an abnormal rate is when the server is formatting a floppy disk. DOS is not available during a disk format to service requests coming in from clients. As a result, many retries will be made from client machines causing the number of server-busy packets to increase. Server Cache Hits Percentage of requests serviced by the cache rather than accessing DOS. The cache will not be used for smaller files. If the server can service the incoming packet in one request, it will not use the cache. Usually files under 1024 bytes will not take advantage of the cache. The cache is directly related to the number and size of the read buffers. If the percentage is low, an increase of the number of read buffers may speed up the process. Packets Received The total number of packets received by the server. Bad Packets Received This number represents the number of times the server got a packet from the IPXODI that was damaged, possibly with a corrupt IPXODI header. Bad packets should rarely be received. If this number is non-zero, there could be a hardware problem, possibly the network board. Watchdog Terminations NetWare Lite uses a process called the watchdog to verify whether a connection exists. In a server's connection table there is a timer associated with each connection. Whenever a packet is received from a client, the timer associated with that client is reset to zero. If no packets are received within five minutes, the server calls that computer by sending out a packet asking for a response. If the client computer responds, the server will reset the timer associated with that connection. If the computer does not answer within five minutes, the server will call again once a minute for ten more minutes. If no response is received from the missing computer, the server will remove the machine from the connection table and the client will have to reestablish a connection to access the server. The process of eliminating missing connections using watchdog terminations is used to keep the connection table in each server as clean as possible. Each client machine has a connection table where the computer keeps track of how many other machines it is connected to. Unlike the server, the client's connection table is not monitored by a watchdog and will not be disconnected if the connection is lost. When a connection is lost with a server, the client machine will return the message "General failure reading device NWLite" and will request the user to abort, retry, or fail every time an operation that accesses the server is attempted while the server is down. When the connection is first reestablished, the user will receive the same error, but pressing <r> for retry will reestablish the connection and carry out the requested operation. Troubleshooting with the Server Status Screen The right columns of the server status screen contain the current configuration, the peak level, and the current statistics of the items configured in the server configuration menu with the exception of Open files. The CFG (configured) setting of Open files is the number of files that are defined in the CONFIG.SYS file that DOS uses to configure the system when booting the computer. The rest of the items have been covered previously in this document. A network administrator may use the three columns of information to fine tune the network. The items in the right hand column affect the size of the network in memory and the way the network operates. By monitoring the figures in the PEAK and CURR columns and comparing those with the number currently configured in the CFG column, a netowrk administrator may avoid wasting valuable memory and verify that the network has plenty of room to operate. If the highest recorded value for any of these attributes approaches 80 percent of the configured setting, a network administrator should consider increasing the configured setting. The number of connections, client tasks, and open files are three figures that need to be monitored regularly. As the highest values for these statistics approach or equal the corresponding configuration settings, unpredictable results can occur. These results can be anything from file locking problems, to data corruption, to the server crashing and locking the entire network. By monitoring the statistics on the Server Status Screen, a network administrator can isolate problems before they become critical, avoid wasting valuable memory space that can be better used by other applications, and tune the network so that it will operate at the most optimal level. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite 1.1 Status Reports DOCUMENT ID#: FYI.P.6072 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NetWare Lite 1.1 Status Reports Network software status reports 1 through 31 are documented in the NetWare Lite manual on pages 138 through 144. The following are additional status reports. Status Report 32: The size of receive buffers specified in the server configuration is too big for the LAN board being used. The receive buffer size was changed to the maximum packet size allowed by the LAN board. Status Report 33: The size of read buffers specified in the server configuration is too big for the LAN board being used. The read buffer size was changed to the maximum packet size allowed by the LAN board. Status Report 34: SERVER.EXE cannot initialize network printer because the number of configured printers is too small. Status Report 35: SERVER.EXE cannot initialize network printer because the number of configured printers is too small. Status Report 36: Selected configuration of SERVER.EXE exceeds 64k of data memory. Use NET.EXE to reduce configuration parameters. Reboot machine now, then reconfigure server with NET.EXE while SERVER.EXE is not loaded. Status Report 37: CLIENT.EXE was loaded before SERVER.EXE. SERVER.EXE should be loaded first if a Network Printer is, or will be, attached to this machine. Status Report 38: Not enough memory to load. Status Report 39: The IO buffer size specified in the server configuration is not a multiple of 16. The IO buffer size was changed to a multiple of 16. Status Report 40: The IO buffer size specified in the server configuration is not a valid multiple of the receive buffer size. The IO buffer size was changed to two times the receive buffer size. Status Report 41: The number of IO buffers specified in the server configuration is greater than the number of connections. The number of IO buffers was changed to the number of connections. Status Report 42: Byte value greater than 255 in configuration file was truncated. Status Report 43: CLIENT.EXE was not unloaded because no previously loaded CLIENT.EXE could be found in memory. Status Report 44: CLIENT.EXE was not unloaded because the version of CLIENT.EXE in memory is not the same as this one. You must run the same version of CLIENT.EXE to unload it. Status Report 45: CLIENT.EXE was not unloaded because another program was loaded after it. You must unload this other program first to unload CLIENT.EXE. Status Report 46: CLIENT.EXE was unloaded from memory. Status Report 47: Byte value greater than 255 in NET.CFG configuration file was truncated. Status Report 48: Bad route address syntax in NET.CFG configuration file. Status Report 49: SERVER.EXE was not unloaded because it is not currently loaded. Status Report 50: SERVER.EXE was not unloaded because the version of SERVER.EXE in memory is not the same as this one. You must run the same version of SERVER.EXE to unload it. Status Report 51: SERVER.EXE was not unloaded because another program was loaded after it. You must unload this other program first before unloading SERVER.EXE. Status Report 52: SERVER.EXE was unloaded from memory. Status Report 53: This copy of SERVER.EXE is for update use only. SERVER.EXE did not load. Status Report 54: This copy of CLIENT.EXE is for update use only. CLIENT.EXE did not load. Status Report 55: SERVER.EXE was not loaded because an IPX socket could not be opened. Please configure IPX with more sockets before loading SERVER.EXE. Status Report 56: SERVER.EXE was not loaded because NETx.COM has been loaded. Please load SERVER.EXE before loading NETx.COM. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Troubleshooting Lockup (Hanging) Problems DOCUMENT ID#: FYI.P.6074 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Troubleshooting Lockup (Hanging) Problems While using a networking system, problems may be met; locking could be one of them. This document, which is divided into two areas of hardware and software, is intended to help diagnose and resolve lockup problems. Hardware 1. Most Local Area Network (LAN) boards come with the ability to change the IRQ, base I/O address, and memory address settings (in some cases). This is done by either setting switches located on the network board or through a software setup utility. When NetWare Lite is installed, it must be told what the IRQ, base I/O, and the memory address settings are on the board. If the board does not agree with the settings that the network is searching for, it could cause lockups. This usually happens when the network board driver is loaded, when SERVER.EXE is loaded, when CLIENT.EXE is loaded, or when the NET utility is used. The solution for this type of problem is straight forward. The settings on the board need to be determined by checking the switches and sometimes cross referencing it with the documentation provided with the network board. After they are found, the install process is repeated for NetWare Lite and the correct options chosen to correspond to the hardware. 2. Another lockup problem may occur when the IRQ, base I/O address, or memory address conflict with another device in the same machine. Each of these settings must be unique to the network board. Devices that may conflict include modems or mice. Lockups in this case can show up anytime after the network has been loaded. A reference list is provided that contains the IRQ and Base I/O address for many devices. For more information on interrupts, see Fax Document 212 or FYI.P.6054. ┌───────────────────┬────┬──────────────────┐ │ Options │IRQ │ Base I/O │ ├───────────────────┼────┼──────────────────┤ │ Com1 │ 4 │ 3F8-3FF │ │ Com2 │ 3 │ 3F8-2FF │ │ LPT1 │ 7 │ 378-37F │ │ LPT2 │ 5 │ 278-27F │ │ VGA │ 2 │ 3C0-3CF │ │ EGA │ 2 │ 3C0-3CF │ │ CGA │ │ 3D0-3DF │ │ Hercules │ │ 3B4-3BF │ │ Mono │ │ 3B0-3BF │ │ AT controller │ 14 │ 1F0-1F8, 170-177 │ │ Floppy controller │ 6 │ 1F0-1F8, 3F0-3F7 │ │ Tape controller │ 5 │ 280-28F │ │ XT controller │ 5 │ 320-32F │ │ │ │ │ └───────────────────┴────┴──────────────────┘ Note: Along with the above mentioned I/O address conflicts, address 360 should be avoided. This address may overlap with beginning address 378 that is used in LPT1 processes. (This is hardware defined and may depend on the particular network board used.) The best solution for this is to configure the network board I/O address at 300, 320, or 340. These settings will work for most systems. 3. The switch settings on the board are not the only things that can cause problems. Some network boards, when not fully compatible with Novell certified boards, can also cause problems. When locking problems do not seem related to any of the settings on the board, try using a different board to see if it does clear up. Occasionally, a bad board is met. Software 1. Some software can cause a lockup when it is simply not compatible with NetWare Lite. These programs usually use protocol that tries to print, gain access to RAM, or gain access to the hard drive without going through DOS. Because NetWare Lite is written to work with DOS these programs cannot be used. 2. NetWare Lite is a memory resident program and occupies part of RAM. This limits the amount of room allowed for other programs. When conventional memory is too low, it can cause applications to crash. One solution for this is to load as much into upper memory. Out of the files loaded through the STARTNET.BAT file, all but SERVER.EXE can be loaded high. This is done in MS-DOS 5.0 by putting "loadhigh" before the file name to be loaded. This is done in DR-DOS 6.0 by putting "hiload" before the file name to be loaded. (Third-party memory managers may also be used but not loaded at the same time with other memory managers.) Note that many memory resident programs can be loaded high but others cannot. If you load a particular program high and find that your system locks more frequently, load it back into conventional memory again. Example for loading most of STARTNET.BAT high using MS-DOS format: loadhigh lsl loadhigh ne2000 loadhigh ipxodi a loadhigh share server loadhigh client 3. Some network boards use upper memory for their own processes that range from C000h to E000h. If this is the case, they do not require a memory manager to control them. Furthermore, this area in upper memory should be excluded from the memory manager's control. To do so insert the following in CONFIG.SYS: For MS-DOS 5.0 use: device=c:\DOS\emm386.exe x=mmmm-nnnn For DR-DOS 6.0 use: device=c:\drDOS\emm386.sys /exclude=mmmm-nnnn (mmmm is beginning and nnnn is the ending address.) Note: Most network-board drivers occupy about 8 to 16 KB of memory. Check the references for your specific device. 4. CONFIG.SYS also has a parameter that can be changed that may cause computers to lock. That is "files=xx." The xx is the number of files that machine can have open at one time. The suggested amount is 10 files per client plus 30 more. 5. Along the same line as the above paragraph, the number of client tasks could have the same effect. To change the client tasks, you must run the NET utility, go to "supervise the network," then "server configuration." This parameter is normally set between 5 and 10 per client. 6. Terminate-Stay-Resident (TSR) programs can also cause lockups. They can show up in several ways of which most commonly is when the TSR is functioning. It can also happen when the TSR seems inactive. The easiest way to find out if a TSR is causing the lockup is by renaming AUTOEXEC.BAT and CONFIG.SYS and then putting in CONFIG.SYS the following: FILES=30 LASTDRIVE=G If the problem no longer persists, add each component back into AUTOEXEC.BAT and CONFIG.SYS one by one until you find the one that is causing the problem. Modifications may be necessary to make the conflicting TSR work properly, or it may even be incompatible with the network environment. 7. Some incompatibilities have been found with certain hardware and software configurations. NetWare Lite has made some modification to adapt to these systems. These modifications come in the form of a patch that is applied once to each machine in the network. More specifics on these patches can be faxed to you through NetWare Lite's automated Fax Document 263 or see FYI.P.6087. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite v1.1 - Summary of New Features and Enhancements DOCUMENT ID#: FYI.P.6066 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NetWare Lite v1.1 - Summary of New Features and Enhancements NetWare Lite v1.1 has been developed primarily as a maintenance release. NetWare Lite v1.1 increases the stability, compatibility, and performance of NetWare Lite, as well as adding some enhancements and new features. The following is a summary of the new features and enhancements. Note: For complete information concerning any of the features or enhancements summarized in this document, please see the README files on the NetWare Lite v1.1 diskette. NLCache The primary new feature of NetWare Lite v1.1 is a NetWare Lite disk cache called NLCACHE. This cache can be configured to use conventional, extended, or expanded memory and can be enabled and disabled from the DOS command line. NLCACHE dramatically increases the performance of NetWare Lite. Due to the length of the information, please download Fax Document 155 or FYI.P.6075 for more information on how to set up NLCache. ***** WARNING ***** If you choose to use another cache program in place of NLCache, you MUST turn off the deferred rights feature of the cache to avoid possible fragmentation or corruption of data! Note: Do not run two caching programs simultaneously. IPXSYNC NetWare Lite v1.1 ships with a utility called IPXSYNC. Until now, if two workstations, A and B for example, mapped drives to each other in their STARTNET.BAT files, machine A would fail to map drives to machine B because machine B had not yet loaded the network software. (Turning on two or more machines at precisely the same time is almost impossible.) This problem is solved by the IPXSYNC utility. This synchronization utility can be placed in the STARTNET.BAT file to make a Lite workstation pause until all necessary servers have booted and loaded the network software. The IPXSYNC utility works from within the STARTNET.BAT file. It should be run from the STARTNET.BAT file after the server and client but before the drives are mapped and the printers are captured. The syntax is the following: IPXSYNC <string> <number>. Replace <string> with any string that is to be broadcast over the network. Replace <number> with the number of computers that have to broadcast that message before the batch file can continue. Example: There is a network with three computers (all setup as servers and clients) and they all have drives mapped to each other. The network supervisor can put the IPXSYNC utility in the STARTNET.BAT file to ensure all the computers are up and the network is loaded before the drive mappings are attempted. The supervisor should put the line "IPXSYNC Ralph 3" into each STARTNET.BAT file after SERVER.EXE and CLIENT.EXE are loaded. Each computer, when turned on, will wait for the string "Ralph" to be returned from the other two machines before continuing on to map the drives. The user can press any key to terminate the process before the operation is complete, but this will cause the drives not to be mapped because the network was not completely operational at the time. Net Save NetWare Lite v1.1 ships with a new utility called NET SAVE that will save all active drive mappings and port captures on a workstation. The NET SAVE utility is not required but is provided as a convenient way to set up the network environment. At the DOS prompt, type NET SAVE. The mapped drives, captured ports, and DOS environment variables are saved in a file called NLLOGIN.BAT that the user can add to the STARTNET.BAT file. The next time the STARTNET.BAT is executed, the saved drive mappings and port captures will be in effect. The NET SAVE utility is not required but is provided as a convenient way for a network administrator to set up the network environment. Notify NetWare Lite v1.1 ships with a feature called NOTIFY that gives the user the option to be notified when a print job is completed. This feature is useful when the network printer is in a different room than the user who is submitting the print job. The notify feature is activated by placing a "n=y" parameter in the NET CAPTURE statement. The default setting of the notify feature is no. After receiving the message, a user can delete the message by pressing <Crtl>+<Enter> at the same time. Auto Reattach NetWare Lite v1.1 has an AUTO REATTACH feature. Occasionally, a network board momentarily loses its connection with other network boards in the network. For example, a workstation on the network is rebooted. Under NetWare Lite v1.0, when a connection was interrupted, the DOS error message, "General failure reading device NWLite--Abort, Retry, Fail" would be displayed and the user would be required to press "Retry" to reestablish the network connection. NetWare Lite v1.1 automatically attempts to reconnect to the network when a connection is lost. This reattach attempt is transparent to the user provided that the workstation has come back online when the reattach attempt is made. Otherwise, the above-mentioned DOS error message is displayed to alert the user that the connection is no longer available. Net SLIST NetWare Lite v1.1 ships with an enhanced NET SLIST command that will show all available Lite servers without requiring the user to be logged into the network. This feature is helpful to users who wish to know if a particular server is available before continuing with a log in attempt. Dynamic Update of Print Screen The print job screen in the NET utility of NetWare Lite v1.1 is dynamically updated. This is useful to network supervisors who wish to monitor printing activity in real time on the network. Net Send and Net Receive In contrast to NetWare Lite v1.0, NetWare Lite v1.1 messages, which appear on the screen as a result of the NET SEND command or as a result of a completed print job notification, do not suspend the operation of NetWare Lite v1.1 servers. Furthermore, the NET RECEIVE feature allows a user to configure the workstation to cause messages resulting from a NET SEND command to "time out" after a set amount of time. These enhancements are useful to users who wish to run batch processes while away from their workstations without NetWare Lite messages permanently halting those batch processes. To use the NET RECEIVE command, type the following from the command line: NET RECEIVE <number> Replace <number> (0 to 1500) with the number of seconds that you wish the messages to remain on the screen. If you enter 0 (Net Receive 0), the message will remain on the screen until <Ctrl>+<Enter> keys are pressed simultaneously. Note: If you do not use the NET RECEIVE command, the default setting will require a user to press <Ctrl>+<Enter> simultaneously to clear the message from the screen. Note: These enhancements do not apply to Native NetWare broadcasts (NetWare v3.11, for example). If the NetWare Lite network is part of a Native NetWare network, broadcasts from Native NetWare will still suspend both foreground and background processes on the workstation until the message is cleared from the screen. Memory Enhancements The NetWare Lite v1.1 version of SERVER.EXE can be loaded into high memory in contrast to v1.0. CLIENT.EXE, LSL, IPXODI A, and the board driver, can also be loaded into high memory. SERVER.EXE'S default size is approximately 10 KB smaller in NetWare Lite v1.1 than the default size of SERVER.EXE in the v1.0. Both of these enhancements allow additional conventional memory to be available for other applications. The NetWare Lite v1.1 version of SERVER.EXE and CLIENT.EXE can be unloaded from conventional memory (they cannot be unloaded from high memory), by typing the commands SERVER U or CLIENT U. Note: CLIENT.EXE must be unloaded before SERVER.EXE. Larger Print Job Packet Size NetWare Lite v1.1 uses a larger print-job packet size that results in significantly faster printing than v1.0. Net Commands Use the DOS Error Level In NetWare Lite v1.1, all Net commands issued from the command line (NET MAP) set a DOS Errorlevel of zero upon successful completion and non-zero for an unsuccessful completion. This is helpful for verifying that the command completed successfully in a batch file before moving on. Commands Are More Like Native NetWare The NET WHOAMI command replaces the NET INFO command. The NET USERLIST command replaces the NET ULIST command. Also, you can type NET MAP F:= instead of NET MAP F: if you are used to using native NetWare mapping commands. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NLCache DOCUMENT ID#: FYI.P.6075 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NLCache NetWare LITE CACHING BENEFITS NetWare Lite Cache makes your computer run three to six times faster by reducing the time your computer spends waiting for the hard disk. Caching makes your computer run faster and your hard drive last longer. ***** WARNING ***** NetWare Lite Cache should not be used concurrently with another caching software. If you choose to use a different cache program instead of NLCache, you must disable the cache's delayed writes in NLCINST under Deferred write delay; together they may cause problems. HOW NetWare LITE CACHE WORKS NetWare Lite Cache keeps copies of data read from the disk in a memory area called a cache. When a disk read is requested, NetWare Lite Cache checks to see if the data is already in the cache. If it is, NetWare Lite Cache delivers the data directly from the cache. If it is not, the disk read is performed and a copy of the data is put in the cache. NetWare Lite Cache's LookAhead option adjusts the disk transfers to cache data even before you need it by reading entire blocks of sectors for future use. LookAhead makes big improvements in disk throughput even with a small cache. When disk writes are requested, NetWare Lite Cache determines if the data is in the cache and if it has changed. If it has not changed, (determined by checksum) NetWare Lite Cache does not rewrite data to the disk. NetWare Lite Cache's optional delayed write feature speeds up disk operations even more by combining multiple disk writes into a single write. Also, NetWare Lite Cache can turn off the delayed write feature (in NLCINST) and function as a write-through cache. If you have a power failure or reset the machine when using the delayed write feature, you may lose data because the data written to the cache in RAM is not written to the hard disk or floppy disk until the delayed write is complete. When using delayed write, always exit programs correctly. The NetWare Lite NLCINST program helps you select the correct cache program for the type of memory your computer uses. ■ NLCACHEC is for computers with only conventional memory (memory up to 640 KB). ■ NLCACHEX is for computers with extended memory (memory above conventional, starting above 1024 KB). ■ NLCACHEM is for computers with expanded memory (special or paged memory that requires a device driver). You can use only one disk caching program at a time. If your computer has expanded memory and extended memory, use either NLCACHEX or NLCACHEM. INSTALLING NetWare LITE CACHE The NetWare Lite Cache programs are copied to your hard drive when you initially install NetWare Lite. If you specify that you want to use the NetWare Lite cache during installation, the proper command will be automatically added to the STARTNET.BAT file--the file that loads the network into memory. The INSTALL program recognizes the type of memory (conventional, expanded, extended) that your computer has and how much memory is available. If your computer has 1 MB or more of free memory, the INSTALL program defaults the "Use NLCACHE and load it from STARTNET.BAT" option to YES. (This option is under STEP 2 "Preview changes to DOS startup files.") If you want a cache, leave the option set to YES. A NetWare Lite Startup command line, which includes the applicable NetWare Lite Cache program name (NLCACHEC, NLCACHEX, or NLCACHEM) and a number equal to half of the free memory (for the cache), will be included in STARTNET.BAT. When STARTNET.BAT is run, the cache program loads using half of the free memory for the cache area. If you do not want a cache, change the option to NO. To create or modify the cache-startup command line from the DOS prompt, type NLCINST. The current cache-startup command line (if any) will be displayed. Follow the instructions on the screen. You can stop modifying or creating the cache-startup command line at any time by pressing <Esc> repeatedly until the DOS prompt appears. The new startup selections will take effect the next time you boot your computer. INSTALLING AS A TSR If you put the cache startup command in batch file like AUTOEXEC.BAT, STARTNET.BAT, or manually type it at the DOS prompt, NetWare Lite Cache will be loaded as a TSR. When NetWare Lite Cache is loaded as a TSR, it can be unloaded by using the /Q option. If you put the cache startup command in CONFIG.SYS, NetWare Lite Cache is loaded as a device driver and cannot be unloaded with the /Q option. INSTALLING AS A DEVICE DRIVER You must use DOS 3.0 or higher to load the cache as a device driver. NetWare Lite Cache requires slightly less memory when it is loaded as a device driver than when it is loaded as a TSR. (DOS assigns TSRs a copy of the environment and a 128 byte control block. Device drivers do not have a copy of the environment or the 128 byte control block). Start NetWare Lite Cache as a device driver by putting one of the following commands in your CONFIG.SYS file: KEY TERMS [path] Directory where the NetWare Lite Cache programs are located. [size] Amount of memory (specify kilobytes) you want to allocate to the cache. If you do not specify a value, NetWare Lite Cache uses all free memory for the cache. [start] Starting address in extended memory for the cache. Extended memory addresses begin above 1024 KB. If you do not specify a starting address, NetWare Lite Cache uses the first available memory area. This is the best choice for most installations because it allows NetWare Lite Cache to put the control tables into extended memory. However, you may specify a specific address for NetWare Cache to use. [options] One or more startup command options. See the "Cache Startup Commands" section of this document. If you put the cache startup command in your CONFIG.SYS file, NetWare Lite Cache loads as a device driver each time you boot your computer. (Remember, as a device driver, it can not be unloaded with the /Q option.) All other control options work as described in the "NetWare Lite Cache Control" section of this document. To Manually Create or Modify the Cache Startup Command as a TSR, start the NetWare Lite Cache program by entering the cache-startup command line at the DOS prompt or by including it in either AUTOEXEC.BAT or STARTNET.BAT. TYPE OF DEVICE DRIVER CACHE STARTUP COMMAND MEMORY Conventional Format: DEVICE=[path] NLCACHEC.EXE [size] [options] Example: DEVICE=C:\NWLITE\NLCACHEC.EXE 128 /T=2 (The cache size would be 128 KB. The maximum write delay would be 2 seconds.) Extended Format: DEVICE=[path] NLCACHEX.EXE [size] [start] [options] Example: DEVICE=C:\NWLITE\NLCACHEX.EXE 2048 D000 /T=5 (The cache size would be 2048 KB. The starting address would be D000. The maximum write delay would be 5 seconds.) Expanded Format: DEVICE=[path] NLCACHEM.EXE [size][options] Example: DEVICE=C:\NWLITE\NLCACHEM.EXE 512 /T=5/B=16 (The cache size would be 512 KB. The maximum write delay would be 5 seconds. The LookAhead buffer size would be 16 KB.) TYPE OF TSR CACHE STARTUP COMMAND LINE MEMORY Conventional Format: NLCACHEC [size] [options] Example: NLCACHEC 128 /T=5 (The cache size would be 128 KB. The maximum write delay would be 5 seconds.) Extended Format: NLCACHEX [size] [start] [options] Example: NLCACHEX 1024 D000 /T=2 (The cache size would be 1024 KB. The starting address would be D000. The maximum write delay would be 2 seconds.) Expanded Format: NLCACHEM [size] [options] Example: NLCACHEM 512 /T=2 (The cache size would be 512 KB. The maximum write delay would be turned off so the cache becomes a write-through cache.) CACHE STARTUP COMMANDS /A= Sector Chain Limit ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ It suppresses caching of read/write requests larger than the limit value. The limit value range is from 1 to 128 sectors (128 sectors is the maximum number of sectors DOS allows). ■ Use it to tune the cache for unusual cases where programs are effectively flushing your cache by doing large reads. If you select a sector limit value less than the maximum (128), large reads are not cached. ■ If this is not used, NetWare Lite Cache selects a best-fit limit value. For cache sizes smaller than 256 KB, a /A= value larger than the best fit value is ignored. /B= LookAhead Buffer Size ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ It specifies the size of the LookAhead buffer (specify kilobytes). The LookAhead buffer requires that you allocate additional conventional memory to the size of the LookAhead buffer. The LookAhead Buffer is used during sequential disk accesses to improve computer performance. NetWare Lite Cache continually monitors your disk activity and turns LookAhead on and off according to the type of reads being done. When you are performing sequential reads, NetWare Lite Cache reads large blocks of sectors into the LookAhead buffer. This saves time by anticipating future reads and combining them with reads that have already been requested. ■ The LookAhead buffer size can be from 0 to 16 KB. Consider a LookAhead buffer size of at least 9 KB. If you specify a LookAhead buffer of zero, both LookAhead buffer size (/B) and the deferred write capability (/T) are disabled. /O Control Table Location ■ Use with NLCACHEX and NLCACHEM. ■ It directs NetWare Lite Cache to use cache memory instead of conventional memory for the cache control tables. This means that more of your conventional memory is available for other applications. ■ The /O option is suppressed if either the HMA (High Memory Area) beginning at address 1024 KB is not available or if the /R options used. ■ The /O option may reduce cache performance (speed) when used with abnormally slow add-on memory boards. /P Place LookAhead in Expanded Memory ■ Use with NLCACHEM. ■ Uses expanded memory (instead of conventional memory) for the LookAhead buffer. ■ The /P option may reduce cache performance (speed) when used with abnormally slow add-on memory boards. /R Disable A20 Latch ■ Use with NLCACHEX. ■ This switch disables the use of CPU latch A20. Only use this option if you have compatibility problems or if your computer hangs for no apparent reason. ■ The /R option may be selected automatically in some computer configurations. /S Assign Cache High ■ Use with NLCACHEX. ■ It places the cache memory at the top of the extended memory. This may be necessary if you are using programs that reallocate extended memory, such as Windows/386, AutoCAD, and Lotus 123 - release 3. If you use this option, NetWare Lite Cache ignores any starting address specification. /T= Maximum Write Delay ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ This switch specifies the maximum delay value for deferred disk writes. The delay value may be from 0 to 5 seconds. Write delay is disabled if you enter a delay value of 0 (/T=0) or if the LookAhead buffer is set to 0 (/B=0). If the maximum write delay value is 0 or if the LookAhead buffer value is zero, NetWare Lite Cache operates as a write-through cache. The deferred write feature speeds up your computer in two ways: 1. It groups multiple small-write requests into fewer large-write requests. 2. It avoids repetitive writes to the same sectors. DOS spends much of its time writing and rewriting the same File Attribute Table (FAT) sectors on your disk. When deferred writes are pending and a new write request is made for the same sectors, the new write data replaces older data so the physical write is performed once with the most recent changes. /U Nonconforming Partition ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ Certain schemes for partitioning hard disks larger than 33 MB do not handle the disk BIOS interrupts correctly. If the disk BIOS interrupts are handled incorrectly, use the /U option. ■ The /U option is not required for normal DOS disk partitions. If this option is used, only the first 256 MB of each physical disk is cached. /V Disable INT 19 Capture ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ This switch disables normal interrupt line 19 capture. It may solve problems with rare and unusual programs that use interrupt line 19 in a nonstandard manner. /W Disable Duplicate Write Check ■ Use with NLCACHEX and NLCACHEM. ■ This switch suppresses duplicate write-checking that NetWare Lite Cache normally uses to avoid rewriting cached sectors that have not changed. The checking logic may produce false compares when used with abnormally slow add-on memory boards. If your computer stops when the cache is started, try using this option. /X Disable Memory Diagnostic ■ Use with NLCACHEX and NLCACHEM. ■ When you start NetWare Lite Cache, it normally performs a brief memory diagnostic check. If you use this option, the memory check is skipped. /Y Enable 8088/86 High Memory Transfers ■ Use with NLCACHEC and NLCACHEM. ■ It enables the caching of disk transfers to or from memory addresses above B000:0000 on 8088/8086 computers. If this option is not used when NLCACHEC is running, transfers are not cached due to the potential hardware DMA (Direct Memory Access) channel unreliability. /Z Disable Snooze Alarm ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ This switch disables NetWare Lite Cache's snooze alarm. The snooze alarm generates a low-pitched beep if NetWare Lite Cache is unable to find a safe time slot to complete a deferred write. The alarm sounds every 5 seconds until pending deferred writes are completed. NetWare LITE CACHE CONTROL After NetWare Lite Cache is started, you can control its operation by executing a cache control command. The control command consists of the name of the caching program and a control option. For example, if you use NLCACHEX and want to get help on NetWare Lite Cache options, type the following: NLCACHEX /HELP <Enter> Cache Control Commands /HELP ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ This switch displays parameters and options that can be used in the cache-startup command line and lists the cache control commands. /Q Quit ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ If NetWare Lite Cache was started as a TSR from the DOS prompt or batch file, this option terminates the NetWare Lite Cache program and attempts to release all memory it was using. If other TSR programs were loaded after NetWare Lite Cache, NetWare Lite Cache's conventional memory may be locked. If this happens, you may be able to quit NetWare Lite Cache by unloading the TSR programs that were loaded after NetWare Lite Cache and trying the /Q command again. ■ If NetWare Lite Cache was started from your CONFIG.SYS file as a device driver, this option has no effect. Device drivers cannot be removed from memory. The only way to take a device driver out of memory is to remove its "device=" statement from your CONFIG.SYS file and reboot your computer. - Disable and Flush ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ Flushes the cache buffers and disables the cache. When the cache is disabled, hard disk reads and writes are performed as if the cache was never loaded. The cache remains in memory and can be enabled with the "+" option. + Enable and Flush ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ This switch flushes the cache buffers, resets the cache statistics to 0, and enables the cache if it was previously disabled with the "-"option. ? Status ■ Use with NLCACHEC, NLCACHEX, and NLCACHEM. ■ Displays cache status. The top portion of the status screen displays: 1. Cache size 2. Drives being cached 3. Current cache options ■ In some cases, NetWare Lite Cache may selectively enable certain options, even though these options were not specified on the cache startup command. If the cache has been disabled with the "-" option, the screen displays "cache is inactive." If "cache is inactive" is followed by an error code, a serious problem exists. An error code 99 indicates that some other program is writing into NetWare Lite Cache's control tables. Any other error code indicates a problem with your add-on memory. The Disk Usage Statistics show the following: 1. Number of read requests that DOS made 2. Number of physical disk reads that were performed 3. Percentage of reads saved because the data was in the cache 4. Number of write requests that DOS made 5. Number of physical disk writes actually performed 6. Percentage of disk writes saved because they were duplicated writes or the data had not changed The Error Statistics show the following: 1. Number of cache memory errors 2. Number of disk transfer errors 3. Number of errors ignored by the user Memory Errors are tallied whenever an error is detected in your extended or expanded memory subsystem. Disk errors are tallied whenever an error is reported by your disk drive subsystem. Errors ignored by users are tallied when a disk error is detected while performing a deferred write and a user enters an ignore response at the "Retry or Ignore" prompt. MEMORY REQUIREMENT The resident conventional memory size required by NetWare Lite Cache is the total of the following: ┌────────────────────┬────────────────┬──────────────┬────── ────────────┐ │ SIZES │ NLCACHEC │ NLCACHEX │ NLCACHEM │ ├────────────────────┼────────────────┼──────────────┼────── ────────────┤ │Cache Program Size │ 8 KB │ 8 KB │ 8 KB │ ├────────────────────┼────────────────┼──────────────┼────── ────────────┤ │LookAhead Buffer │ See /B option │ See /B option│ Note 1 Below │ │Size │ │ │ │ ├────────────────────┼────────────────┼──────────────┼────── ────────────┤ │Cache Size │ The amount of │ NOT │ NOT │ │ │ memory you │ APPLICABLE │ APPLICABLE │ │ │ allocate to │ │ │ │ │ the cache │ │ │ ├────────────────────┼────────────────┼──────────────┼────── ────────────┤ │Resident Control │ │ │ │ │Table Size │ NOT │ Note 2, 3 │ Note 2, 3 Below │ │ │ APPLICABLE │ Below │ │ ├────────────────────┴────────────────┴──────────────┴────── ────────────┤ │Note 1: LookAhead buffer size may be controlled with the /B= option. │ │ If the /P option is active (see "Cache Startup Commands"), │ │ the LookAhead buffer is placed in the EMS memory. No │ │ resident conventional (base) memory is required for the │ │ LookAhead Buffer. │ │ │ │Note 2: If the /O option is active, cache sizes up to 5.3 MB require │ │ no resident control table memory. If your cache size exceeds │ │ 5.3 MB, multiply the cache size in megabytes by four to get │ │ the resident control table size in kilobytes. │ │ │ │Note 3: If the /O option is not active, the resident control table │ │ requires 12 KB for each megabyte of cache memory. │ └─────────────────────────────────────────────────────────── ────────────┘ COMPATIBILITY NetWare Lite Cache is fully compatible with the XMS protocol, DOS network protocols, DesqView, Windows 3.1, and earlier Windows versions, and it operates with PC, XT, AT, and PS/2 compatible computers under MS-DOS and PC-DOS versions 2 through 5, DR DOS 6.0, and Windows 3.0 and 3.1. If you use a "Load High" memory manager such as 386MAX or QEMM, you may load the cache high. Even though this can be done, it may seriously impair cache performance when used with abnormally slow add-on memory boards. ERROR MESSAGES General Start-Up Errors ■ "Already loaded" -- NetWare Lite Cache is already loaded. ■ "Amount not numeric" -- Invalid size value specified. ■ "Data Compare Error at location hhhhh" -- hhhhh is a hexadecimal memory address. An error was detected during the memory diagnostic. ■ "Invalid command line option" -- Improper command line option specified. ■ "No compatible fixed disk!" -- No compatible disk found. ■ "No Extended Memory available" -- Either your computer has no extended memory installed, or another process is using all the extended memory. ■ "A different NLCache is running" -- A different version of NetWare Lite Cache caching program is already installed. ■ "Too many drive letter options!" -- You are attempting to cache more drives than allowed. ■ "Unsupported sector size!" -- NetWare Lite Cache supports only sector between 512 and 16384 bytes. NLCACHEX Specific Start-Up Errors ■ "Insufficient Extended Memory" -- There is not enough extended memory available to start the cache. ■ "HMA is not available" -- The High Memory Area at location 1024 is in use by another program. The cache control tables will be located in resident conventional (base) memory. ■ "XMS Error Code\ xx" -- xx is an error code returned by the extended memory manager. This indicates a serious malfunction in the XMS manager. The most common error codes are the following: 80 -- function not implemented 81 -- a VDISK device was detected 82 -- an A20 error occurred 8e -- a general driver error occurred 8f -- unrecoverable driver error occurred A0 -- all extended memory is allocated A1 -- all extended memory handles used A2 -- invalid handle A9 -- a parity error occurred NLCACHEM Specific Startup Errors ■ "Expanded Memory content does not match data as written" -- An error was detected during the cache start-up memory diagnostics. You may have a hardware malfunction. ■ "Insufficient Expanded Memory free" -- All expanded memory is in use by other programs. ■ "No Expanded Memory Manager" -- Install the expanded memory manager software you received with your computer or with your expanded memory board. Status Errors ■ "Cache is inactive: Error 99 at (location)" -- The cache tables have been overwritten by another program that is accessing memory outside its allocated region. This condition may be caused by a faulty Terminate-and-Stay Resident (TSR) program or by a normal program addressing memory out-of-bounds. You can identify the offender by removing programs one at a time until the problem goes away. ■ "Cache is inactive: Error xx" -- xx is the error code given by the EMM or LIM driver. If NLCACHEM is unable to save the EMS page map due to repeated errors from the EMS driver, the cache shuts down. There may be a serious problem with the EMS board or the EMM driver software. Errors When Quitting ■ "Cannot release resident memory" -- Other programs are loaded above NetWare Lite Cache. You must unload these programs before quitting the cache. ■ "Cannot remove device driver" -- NLCache was loaded as a device that cannot be unloaded with the /Q option. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DOS Memory Managers and NetWare Lite v1.X DOCUMENT ID#: FYI.P.6076 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM DOS Memory Managers and NetWare Lite v1.x Note: Information listed in this document is intended for use on 386 or 486 based computers. For information on other machines, please consult your DOS manual. This document is intended to aid the user in the basic steps of loading NetWare Lite items into upper memory. General Information This basic summary is necessary to understand how to create the best performing servers and clients with NetWare Lite. Random Access Memory (RAM) in 386 and 486 computers has a uniform structure. The first 640 KB of memory is known as conventional memory, the location where applications load. The next 384 KB of memory is known as upper memory, where system files and other files (such as mouse drivers or network drivers) can be loaded if memory management software is used. On machines with more than 1 MB of RAM, the first 64 KB of memory above 1 MB is known as the High Memory Area (HMA). NetWare Lite v1.0 has several files that may be loaded into upper memory. These files are normally loaded from the STARTNET.BAT file found in the NWLITE directory. These files are: LSL.COM, your network board driver (such as NE2000.COM), IPXODI A, SHARE (found in your DOS directory) and CLIENT.EXE. The proper syntax for loading these files into upper memory depends on which version of DOS and memory manager you choose to use. The following steps instruct you how to load NetWare Lite files into upper memory by using memory managers from DR DOS 6.0 and MS DOS 5.0. If you have any questions that are not answered in this document, please consult your DOS documentation. The memory manager, EMM386, will relocate software into upper memory. Without the use of the EMM386 manager, the only memory that can be used is conventional memory (the first 640 KB of memory). DR DOS 6.0 The memory manager included with DR DOS 6.0 is EMM386.SYS. To load drivers and programs into upper memory, several steps must be followed. Note: EMM386.SYS cannot be used with other memory managers. 1. The following is an example of a CONFIG.SYS file that is configured to allow access to upper memory (UMB) and HMA: HIDOS=ON DEVICE=C:\DRDOS\EMM386.SYS /F=AUTO /B=FFFF /R=AUTO /E=[START-END] HIDOS=ON In the CONFIG.SYS file, the HIDOS=ON line should be included. This allows the computer to put information into HMA if memory is available. EMM386.SYS [/F=AUTO] Performs an automatic search through upper memory for a free 64 KB window. This is the default. [/B=FFFF] Relocates the DR DOS kernel, freeing space in conventional memory for use by applications. By using the ffff location of memory, the kernel will be placed into HMA (if available). [/R=AUTO] Copies data and code from Read Only Memory (ROM), which is slow to run, into Random Access Memory (RAM), which is very fast. [/E=[START-END]] Excludes an area of upper memory from the area being checked for availability of use. This switch should be used if an item uses a specific memory location. For example: If your network board had a memory address setting of CC00 and you used the switch [/E=CC00-CFFF], then the EMM386.SYS driver would not allow any software to occupy the same area of memory. This is a solution to random errors (the machine lockup) that may occur if the network board driver is overwritten. 2. To load NetWare Lite required files into high memory in your STARTNET.BAT file, your syntax should be similar to the following: NetWare LITE v1.1 NetWare LITE v1.0 HILOAD LSL HILOAD LSL HILOAD NE2000 HILOAD NE2000 HILOAD IPXODI A HILOAD IPXODI A HILOAD SHARE HILOAD SHARE HILOAD SERVER SERVER HILOAD CLIENT HILOAD CLIENT Note: Server should not be loaded into high memory with v1.0 3. To examine where your items are loaded into high memory, type the following from the DOS prompt: MEM /A /P (/A shows all information. /P pauses at the end of every screen.) 4. From this screen you will be given several screens of information. To determine what is located in upper memory, be aware that the address A000:0000 is where conventional memory ends and upper memory begins and FFFF:0000 is where upper memory ends and the high memory area begins. For complete information on the MEM command, please refer to page 258-259 of the DR DOS 6.0 User's Guide or call the DRI Automated Fax system at 1-408-649-2344. The titles pertaining to memory management are the following: Document Title 1000 Master Index (A Complete Listing of all Files on the DRI Fax System.) 1300 DR DOS 6 Memory Management overview 1301 Basic Memory optimization 1302 Trouble shooting 1303 Using Third-party memory managers 1305 XMS-EMS memory pool 1306 Preventing DR DOS from loading into HMA 1307 The MEM /A Command 1308 Gate A20 and Printing Problems MS-DOS 5.0 The memory manager included with MS-DOS 5.0 is EMM386.EXE. To load drivers and programs into upper memory, several steps must be followed. In the CONFIG.SYS file, device drivers for HIMEM.SYS and EMM386.EXE must be included and be placed in a specific order. To ensure the proper setup, it is best to have the device line containing HIMEM.SYS at the beginning of the CONFIG.SYS file. The second line should contain the EMM386.EXE line, and the third line should contain a specification of where to load the DOS system files. For example: DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE /X=MMMM-NNNN NOEMS DOS=HIGH,UMB HIMEM.SYS Generally, the default specifications for HIMEM.SYS are sufficient for your system. The main exception is the /MACHINE:XXXX specification, where XXXX is your machine type. Please see page 611 in the MS-DOS 5.0 User's Guide for complete information. EMM386.EXE Switches included with EMM386.EXE that are most commonly used to increase system performance are the following: [X=[MMMM-NNNN]] The MMMM-NNNN denotes an address that EMM386.EXE will not be allowed to use. This is very useful for excluding the address of your network-board driver so it will not be overwritten by DOS. (If the board memory address is set at CC00, the switch would be X=CC00-CFFF.) [NOEMS] Allows access to upper memory and prevents access to expanded memory. It does allow access to extended memory. Other switches can be found in the MS-DOS 5.0 User's Guide on pages 605-609. DOS The HIGH switch allows DOS to relocate the system files into a location called the HMA (High Memory Area), freeing up more conventional memory space. The UMB (Upper Memory Block) switch is for linking conventional memory with upper memory. It is necessary to load drivers or devices into upper memory. Remember, to load any command high, the line must follow the three lines listed above. The command to load a device high in the CONFIG.SYS file is DEVICEHIGH. The command to load an item high in the AUTOEXEC.BAT file or any .BAT file is LH or LOADHIGH. To load the required NetWare Lite files into high memory in your STARTNET.BAT file, your syntax should be similar to the following: NetWare LITE v1.1 NetWare LITE v1.0 LH LSL LH LSL LH NE2000 LH NE2000 LH IPXODI A LH IPXODI A LH SHARE LH SHARE LH SERVER SERVER LH CLIENT LH CLIENT Note: Server should not be loaded into high memory with v1.0 To examine where your items are loaded into high memory, from the DOS prompt type the following: MEM /C |MORE (/C classifies programs by memory usage. It also displays conventional memory and upper memory in separate blocks to easily determine where programs are loaded; the |MORE command pauses at the end of every screen.) For further questions and concerns about loading software into upper memory, consult the MS-DOS 5.0 User's Guide. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite 1.1 and Windows 3.1 Compatibility DOCUMENT ID#: FYI.P.6077 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: FYI.P.6061 SYMPTOM NA ISSUE/PROBLEM NetWare Lite 1.1 and Windows 3.1 Compatibility Installing Windows 3.1 on a NetWare Lite Network: If you are upgrading from a previous version of Windows to Windows 3.1, Novell recommends that you delete the previous version of Windows from your hard drive before you begin installation of Windows 3.1. This is recommended because Windows 3.1 handles many of the settings in the initialization files (*.INI) differently than before and will not always convert these parameters to the new format. There are also many drivers, including all printer drivers, that have been changed from version 3.0 to version 3.1. By deleting any previous version of Windows before you install version 3.1, you ensure that all drivers will be upgraded to the correct versions. The first section of this document describes installing Windows 3.1 on NetWare Lite v1.1 in both Stand Alone and Shared Network versions. The second section, entitled DR DOS 6.0 Configuration Items, discusses general suggestions for configuring DR DOS 6.0, NetWare Lite v1.1, and Windows 3.1 to have a peak performance among the three. The last section, Tips for Running Windows 3.1, describes general items regarding Windows 3.1 and NetWare Lite v1.1 regardless of what operating system you are using. Installing Windows 3.1 Installing a Stand Alone Version of Windows 3.1 Follow the regular installation procedures to install Windows 3.1 as a stand alone version. To be able to access network resources, run the setup program and select "No Network Installed" as the network type. For more information, refer to the Getting Started with Microsoft Windows booklet included with Windows 3.1. Installing a Shared Version of Windows 3.1 The following is intended for users who want to install windows in shared mode. You will need to follow the steps to install on a NetWare Lite Server then for a NetWare Lite Client. Please refer to the Getting Started with Microsoft Windows booklet, pages 6 to 12, for information about installing Windows on networks in general. Steps for Configuring a Server: 1. Decide which Server you want to install the shared copy of Windows on. Note: There must be approximately 16 MB of hard disk space available on the server to install a shareable copy of Windows 3.1. 2. Insert the Windows DISK 1 in the disk drive, and go to that drive (a: <Enter>). 3. Type SETUP /A. When Windows asks for the network path to which it should install, type C:\WINDOWS or some other path to which you want to install Windows. (If this directory does not exist, Windows will create it for you.) As you follow the prompts, a shareable copy of Windows will be installed on the server. Note: This will not create an executable copy of Windows. It merely creates a location where clients can pull the executable programs from after they have been set up (see steps for clients, below). After the shared copy of Windows has been installed, the following steps must be taken to properly configure the network software on the server. 4. Enter the NetWare Lite menu utility by typing NET and pressing <Enter>. Then select "Supervise the network" and then "Network directories" options. Create a network directory by pressing the <Insert> key. Select the server where the WINDOWS directory is located. Type a name for the network directory. Then enter the path to which you installed Windows, from step 3 above. Press <Esc> to exit and save the changes, and exit back to the Main Menu. 5. At the Main Menu in the NET utility, select "Supervise the Network" and then select "Server Configuration." The CLIENT TASKS option defaults to 10 at the time of NetWare Lite installation. Set the CLIENT TASKS in the FUTURE column to 15 per machine connected to the network. (For example, if you had three computers on the network, you would set the client tasks to 45.) 6. When NetWare Lite is installed, the FILES=xx in the CONFIG.SYS file is set to be at least 30. This needs to be increased on the server by 20 per machine connected. You can change this by using a text editor (such as DR-DOS 6.0 EDITOR) to edit the CONFIG.SYS file. 7. After you have performed these steps for the server, reboot the server for these changes to take effect. Steps for Configuring a Client: There are three ways to set up Windows from the shared copy installed on the server in the steps above. Please refer to page 7 in Getting Started with Microsoft Windows for a further explanation of the three methods. Option A. Copy all Windows 3.1 files to the Client machine's hard drive. Setting up Windows in this way will give each user the fastest performance of Windows. However, it will also greatly increase the amount of disk space used and force all clients to have their own hard disks. Option B. Copy only custom configuration files to the Client machine's hard drive. All other files will be run from the shared copy installed on the server in the steps above. Setting up Windows in this way will take up less disk space than option A above. However, it will run slower and client machines still must have their own hard disks. Option C. No files will be stored on the Client machine's hard drive. Instead, the custom configuration files will be stored in a subdirectory on a network server and all other files will be run from the shared copy of Windows installed on the server in the steps above. Setting up Windows in this way is the most conservative as far as disk space is concerned. It also gives the option of leaving the client machines as "diskless workstations," or machines without hard disks. However, it is also the slowest way to run Windows because everything must be pulled off the network any time Windows is run. The steps below are instructions to install Windows from the shared copy using Options A, B, and C above. Option A. Copy all files to the Client machine's hard drive. 1. Load NetWare Lite by typing STARTNET. Map a drive to the network directory that was created on the server in the Steps for Configuring a Server listed above. For example, if the Network Directory you created in step 4 above was WIN31, you would type the following: NET MAP I: WIN31 <Enter> 2. Change to the drive you mapped (I: in this example) I: <Enter> 3. Type SETUP and press <Enter>, and follow the prompts to install a copy of Windows to your local drive. When prompted to either run an Express Setup or a Custom Setup, choose Custom. The custom setup allows you to preview the changes that are being made to the different files on your computer. Refer to Windows documentation for questions regarding the installation. 4. When Windows prompts you, choose to "let you make the modifications later" option. You will then be prompted with a path and file name in which to place a file with Windows-proposed changes to your AUTOEXEC.BAT and CONFIG.SYS files. Depending on which version of DOS you are using, you will need to make certain changes after installing Windows. DR DOS 6.0 None of these changes are necessary if you are running DR DOS. You will only need to verify, after installing Windows, that the subdirectory to which you are installing Windows is in the PATH= statement in your AUTOEXEC.BAT file. MS-DOS If you are running MS-DOS, you will want to look at the Windows-proposed AUTOEXEC.BAT and CONFIG.SYS files, to see the changes that it wanted to make for you. The changes you will be looking for are the following: In the AUTOEXEC.BAT file, Windows will insert a line to run the SmartDrive disk caching utility. However, there have been some problems running with SmartDrive. See the section on "Third-Party Disk Caches," towards the end of this document. It is suggested that you run with either NetWare Lite NLCache or DR-DOS PCKwik disk cache. In the CONFIG.SYS file, Windows will usually try to include its own memory manager, which includes the HIMEM.SYS file, and the EMM386.EXE file. For MS-DOS this should be fine. However, if you experience memory problems or are running with a different memory manager, you will want to leave these lines how they were before the Windows installation. You will also want to include a line STACKS=9,256 in the CONFIG.SYS file, which is a fix to MS-DOS to handle hardware interrupts. 5. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS or LPT2.DOS, depending on which ports you have captured to network printers, instead of the normal LPT1 and LPT2 ports. See "Network Printing and Windows 3.1" later in this document. In the printer configuration, you will need to turn off the "Fast Printing Direct to Port" option. Printing with this enabled bypasses any DOS calls; therefore, you would not be able to print to network printers. To do this, choose "Connect" at the printer definition window. Turn of the "Fast Printing Direct to Port" option. 6. Continue following the prompts to finish the installation of Windows. After you finish the installation of Windows, you will need to edit the SYSTEM.INI file in the directory to which you installed Windows. See the section "Changes to SYSTEM.INI" towards the end of this document. You will now run Windows from your local drive instead of the I: drive. Verify that the subdirectory on your local drive that you selected in SETUP is included in your AUTOEXEC.BAT file in the PATH= statement, as you will need this to run Windows. Option B. Custom configuration files are copied to the Client machine's hard drive. All other files will be run from the shared copy installed on the server in the steps above. 1. Load NetWare Lite by typing STARTNET. Map a drive to the network directory that was created on the server in the Steps for Configuring a Server listed above. For example, if the Network Directory you created in step 4 above was WIN31, you would type the following: NET MAP I: WIN31 <Enter> 2. Create a subdirectory on the Client's hard drive in which to put the custom files (MD C:\DAVE <Enter>). 3. Go to the network drive containing the Windows files (I: in this example) I: <Enter> 4. Type SETUP /N, then follow the Windows installation instructions. ■ When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Note: At the prompt for the path of the Windows files, enter the subdirectory that you created in step 2 (C:\DAVE). ■ Also, at the configuration screen, select the "No Network Installed" Network option. 5. When Windows prompts you, choose to "let you make the modifications later" option. Then you will be prompted a path and file name in which to place a file with Windows-proposed changes to your AUTOEXEC.BAT and CONFIG.SYS files. Depending on which version of DOS you are using, you will need to make certain changes after installing Windows. DR DOS 6.0 None of these changes are necessary if you are running DR DOS. You will only need to verify, after installing Windows, that the network directory where the shared version of Windows is installed and the user subdirectory to which you installed the custom configuration files (I: and C:\DAVE in this example) are both in the PATH= statement in your AUTOEXEC.BAT file. MS DOS If you are running MS DOS, you will want to look at the Windows-proposed AUTOEXEC.BAT and CONFIG.SYS files to see the changes that it wanted to make for you. The changes you will be looking for are the following: In the AUTOEXEC.BAT file, Windows will insert a line to run the SmartDrive disk caching utility. However, there have been some problems running with SmartDrive. See the section on "Third-Party Disk Caches," towards the end of this document. It is suggested that you run with either NetWare Lite NLCache or DR-DOS PCKwik disk cache. In the CONFIG.SYS file, Windows will usually try to include its own memory manager, which include the HIMEM.SYS file, and the EMM386.EXE file. For MS-DOS this should be fine. However, if you experience memory problems or are running with a different memory manager you will want to leave these lines how they were before the Windows installation. You will also want to include a line STACKS=9,256 in the CONFIG.SYS file, which is a fix to MS-DOS to handle hardware interrupts. 6. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS, or LPT2.DOS, depending on which ports you have captured to network printers instead of the normal LPT1 and LPT2 ports. See the "Network Printing and Windows 3.1" section later in this document. In the printer configuration, you will need to turn off "Fast Printing Direct to Port" off. Printing with this enabled bypasses any DOS calls; therefore you would not be able to print to network printers. To do this, choose "Connect" at the printer definition window. Turn off the "Fast Printing Direct to Port" option. 7. Continue following the prompts to finish installing Windows. After you finish the installation of Windows, you will need to edit the SYSTEM.INI file in the subdirectory to which you installed Windows custom configuration files (C:\DAVE in this example). See the "Changes to SYSTEM.INI" section towards the end of this document. Once you reboot, load the network by typing STARTNET. Then, once you have performed your drive mappings and printer captures, you can type WIN to enter Windows. Option C. No files will be stored on the Client machine's hard drive. Instead, the custom configuration files will be stored in a subdirectory on a network server and all other files will be run from the shared copy of Windows installed on the server in the steps above. 1. Load NetWare Lite by typing STARTNET. Map a drive to the network directory that was created on the server in the "Steps for Configuring a Server" section listed above. For example, if the Network Directory you created in step 4 above was WIN31, you would type the following: NET MAP I: WIN31 <Enter> 2. Create a subdirectory on the Server's hard drive in which to put the custom files (MD C:\STEVE <Enter>). 3. Create a network directory that looks at the user's subdirectory by doing the following: ■ Enter the NetWare Lite menu utility by typing NET and pressing <Enter>. ■ Then select the "Supervise the network" then "Network directories" options. ■ Create a network directory by pressing the <Insert> key. ■ Select the server on which you want to store your custom files. ■ Enter the path of the subdirectory you created in step 3, such as C:\STEVE. 4. Map a drive to this network directory: NET MAP G: STEVE <Enter> 5. Go to the network drive containing the Windows files (I: in this example). I: <Enter> 6. Type SETUP /N then follow the Windows installation instructions. ■ When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Note: At the prompt for the path of the Windows files, enter the drive you have mapped to the custom files network directory from step 4 above (in this example it would be G:). ■ Also, at the configuration screen, select the Network option "No Network Installed." 7. When Windows prompts you, choose to "let you make the modifications later." You will then be prompted a path and file name in which to place a file with Windows-proposed changes to your autoexec.bat and config.sys files. Depending on which version of DOS you are using, you will need to make certain changes after installing Windows. DR DOS 6.0 None of these changes are necessary if you are running DR DOS. You will only need to verify, after installing Windows, that the network directory where the shared version of Windows is installed and the network directory to which you installed the custom configuration files (I: and G:\ in this example) are both in the PATH= statement in your AUTOEXEC.BAT file. MS DOS If you are running MS DOS, you will want to look at the Windows-proposed AUTOEXEC.BAT and CONFIG.SYS files to see the changes that it proposed for you. The changes you will be looking for are the following: In the AUTOEXEC.BAT file, Windows will insert a line to run the SmartDrive disk caching utility. However, there have been some problems running with SmartDrive. See the section on "Third-Party Disk Caches," towards the end of this document. It is suggested that you run with either NetWare Lite NLCache or DR-DOS PCKwik disk cache. In the CONFIG.SYS file, Windows will usually try to include its own memory manager, which include the HIMEM.SYS file, and the EMM386.EXE file. For MS-DOS this should be fine. However, if you experience memory problems or are running with a different memory manager you will want to leave these lines how they were before the Windows installation. You will also want to include a line STACKS=9,256 in the CONFIG.SYS file, which is a fix to MS-DOS to handle hardware interrupts. 8. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS, or LPT2.DOS, depending on which ports you have captured to network printers, instead of the normal LPT1 and LPT2 ports. See the "Network Printing and Windows 3.1" section later in this document. In the printer configuration, you will need to turn off "Fast Printing Direct to Port" option. Printing with this enabled bypasses any DOS calls; therefore, you would not be able to print to network printers. To do this, choose "Connect" at the printer definition window. Turn off the "Fast Printing Direct to Port" option. 9. Continue following the prompts to finish installing Windows. After you finish the installation of Windows, you will need to edit the SYSTEM.INI file in the network directory to which you installed Windows custom configuration files (G: in this example). See the "Changes to SYSTEM.INI" section towards the end of this document. After you reboot, load the network by typing STARTNET. Then, once you have performed your drive mappings and printer captures, type WIN to enter Windows. DR DOS 6.0 Configuration Items: The following items are for maximizing performance of Windows 3.1 on a NetWare Lite network running DR DOS 6.0. 1. To run with Windows 3.1 you must have the DR DOS 6.0, April 92, Update diskettes. Because Windows 3.1 was released after DR DOS 6.0, there were changes made to several DR DOS files to be fully compatible with Windows. 2. If you are using the Super PC-Kwik (SUPERPCK) disk caching utility that comes with DR DOS 6.0, there are certain things you can do to optimize the performance of Windows and NetWare Lite v1.1. First, you will need to have a line in your CONFIG.SYS file that calls the Super PC-Kwik Windows driver, called PCKWIN.SYS. A sample command line for this would be the following: DEVICE=C:\DRDOS\PCKWIN.SYS. There are also a few command line switches that should be changed or added. They are the following: /H- This option needs to be added for compatibility with NetWare Lite. It turns off the advanced reads and writes that can cause data corruption on some networks. There will still be read caching that is performed and not just the advanced reads and writes. /L:xxx /R:xxx Both of these options, if present on the command-line of SUPERPCK, should be removed. PC-Kwik defaults to use all available extended or expanded memory for the disk cache. Then it will, if a request is made by some application such as Windows, turn around and lend up to half of that memory back. That is controlled by these options. However, it is easier to optimize the disk cache with Windows if you can control the exact amount of the cache. For this reason, the next option is used. /S:xxx This option instructs SUPERPCK how much memory to use for its cache, and you don't have to worry about how much is getting lent back. You just tell the cache exactly how much you do want it to use. If you do not include an amount (xxx), the /S: option will default to all available extended memory. The following are suggested amounts of memory to allocate to the cache through the /S: parameter based on the amount of RAM in your machine. ┌──────────────────┬───────────────────────┐ │ AMOUNT OF RAM │ SUGGESTED CACHE SIZE │ ├──────────────────┼───────────────────────┤ │ Less than 2 MB │ Do not use a cache │ │ 2 to 4 MB │ 512 KB │ │ 4 to 6 MB │ 1024 KB │ │ above 6 MB │ 2048 KB │ │ │ │ └──────────────────┴───────────────────────┘ The reason for the small cache sizes is that Windows needs all the memory that it can get to perform at its peak. By taking RAM away from Windows and allocating it to a cache, Windows may be forced to use a swap file on disk where it could have run more from RAM if no cache or a smaller cache had been allocated. So by having a small cache, you increase disk performance, and you also leave as much memory available to Windows as possible so that it will be running at an optimum speed. 3. If you have a network board in a 386 or 486 machine that uses a RAM or shared memory address, you need to exclude that address in the memory manager command line. To do this, edit your CONFIG.SYS file and change the EMM386.SYS command. The format will be similar to the following: DEVICE=C:\DRDOS\EMM386.SYS ....(current options)... /E=nnnn-mmmm where /E tells the memory manager (emm386.sys) not to allocate the range from nnnn to mmmm to any other programs. (It is in use by your network board; and you need to make sure that no other programs are loaded at the same memory addresses). nnnn and mmmm represent beginning and ending range addresses for the range to exclude. The following table shows the most common RAM addresses used by network boards, and the values for nnnn and mmmm based on those values. ┌──────────────────────┬──────────────┬──────────────────────── ──────┐ │ MEMORY ADDRESS │ nnnn* │ 8 KB---mmmm*--16 KB │ ├──────────────────────┼──────────────┼──────────────────────── ──────┤ │ C0000 │ C000 │ C1FF C3FF │ │ C8000 │ C800 │ C9FF CBFF │ │ CC000 │ CC00 │ CDFF CFFF │ │ D0000 │ D000 │ D1FF D3FF │ │ D8000 │ D800 │ D9FF DBFF │ ├──────────────────────┴──────────────┴──────────────────────── ──────┤ │ * nnnn indicates starting memory address as found in NET.CFG file.│ │ * mmmm indicates suggested ending address to be used. │ └────────────────────────────────────────────────────────────── ──────┘ Note: If you do not know whether your network board needs 8 KB or 16 KB for shared memory, you should use the larger 16 KB value. Note: If you do not know the memory address your network board uses, you can type the command TYPE C:\NWLITE\NET.CFG and look at the MEM value. (The NET.CFG file instructs your board driver how to initialize your network board.) If you are not using EMM386.SYS in the CONFIG.SYS file, add the following line in the [386Enh] section of the SYSTEM.INI file in your windows directory: EMMExclude=nnnn-mmmm Replace nnnn and mmmm with the values from the tables above. Do not worry if there is already an EMMExclude line in your SYSTEM.INI file. Multiple copies of this line are valid and will operate correctly. Note: For more information on the EMM386.SYS exclude command-line option, please see pages 17 through 19 in the DR DOS 6.0 Customization and Optimization Tips manual. 4. If you are running on a SuperStored drive, be aware that swap files (whether permanent or temporary) cannot exist on a compressed partition of your hard drive. If your entire hard drive is compressed or if not enough room is on the uncompressed partition, you will either have to run without a swap file or go through a few steps to reset your SuperStore partition. Swap files are written to the disk in nonstandard formats. This gives it the benefit of a fast access time. However, swap files may not be created on SuperStored partitions. If you decide you want to have a swap file on your hard drive that is SuperStored and do not have the space on the uncompressed partition, the following steps can help you set up your drive again for use with windows: a. Backup all data on the compressed partition of your hard drive. You will be removing the SuperStor partition; therefore, all data on the hard drive will be erased. If you do not have a backup of your data, you will lose it all. b. Uncompress the drive by running the SuperStore utility (SSTOR) and choosing "remove" to remove the SuperStore partition. Note: If the entire hard disk was SuperStored, you may need to reinstall DR DOS because removing the SuperStore partition will remove any files on your hard disk thus removing your DR DOS files. c. Recreate the SuperStore partition by running SuperStore and choosing "create." When prompted, enter the amount of space to be left uncompressed. You will need to enter this amount in kilobytes ("K"). 1024 kilobytes is equal to 1 megabyte. Remember that this portion of the disk needs to be large enough for your boot files and your permanent swap file. (A 5 MB swap file is a good size.) d. You can now restore your data from your backup copy to your newly compressed SuperStore partition. There is one more thing to remember about SuperStored partitions. When Window searches for the memory manager (EMM386.SYS), it will be looking for the manager in the same path from which it was loaded. You will need to make sure that the EMM386.SYS driver is in the same subdirectory on both the compressed and noncompressed partitions of your hard drive. For example, if the EMM386.SYS file is in the DRDOS subdirectory on your noncompressed partition, make sure that there is a DRDOS subdirectory with the same file in it on your compressed partition. TIPS FOR RUNNING WINDOWS 3.1 Network Operations You should run STARTNET.BAT before entering Windows. You should also map drives and capture ports before entering Windows. Mapped Drives and Connections Windows will display an error message if you try to access a drive on a server that has gone down. Any attempt to access that drive will fail. Under regular DOS, this error is trapped and the client saves enough information to automatically restore the connection to that network directory when the downed server returns to the network. Windows prevents regular DOS from trapping this error. To restore connections to your mapped drive, exit Windows and reissue the NET MAP command when the server is back on the network. Network Printing and Windows 3.1 If you want to print from Windows to a network printer, you must setup the printer in Windows as a printer on port LPT1.DOS (that replaces LPT1.OS2 in Windows 3.0) or LPT2.DOS depending on which port is captured. This is to instruct Windows to use the information that DOS provides it (such as a NET CAPTURE command you may have issued to print to the network printer) to print to LPT1 instead of trying to go to its own physical LPT port. In the printer configuration, you will need to turn off "Fast Printing Direct to Port" option. Printing with this enabled bypasses any DOS calls; therefore, you would not be able to print to network printers. To do this, go into the Control Panel, in Printers, and highlight the printer. This option will show up after highlighting the printer and choosing "Connect." Turn off "Fast Printing Direct to Port" option. You will also want to disable the Print Manager inside Windows for the best printing performance. The reason for this is that using the print manager only makes the print job go through two print spoolers. It passes once through the print manager, and then through the NetWare Lite spooler. This only takes more time and will slow down your printing. NetWare Lite Messages Messages sent to network users through NetWare Lite will not be received if the user to whom you are sending the message is in Windows. Windows Modes If you are experiencing a problem that only occurs when NetWare Lite is loaded and if the problem seems unsolvable, experiment with the other Windows mode to see if the problem is corrected. The Windows mode can be changed by using one of the following command line parameters: Standard Mode: WIN /S Enhanced Mode: WIN /3 (Note that Windows 3.1 does not include an option to run in Real Mode as did version 3.0.) Swap Files Windows 3.1 can use swap files to enhance the performance of multiple tasks. By default, Windows will try to create a swap file on your hard disk at installation. Do not try to create a permanent swap file on a network drive or create temporary swap files on any network drive other than a separate user subdirectory to which other users will not have access. It will corrupt any other swap file that may be in that subdirectory. Every user needs to have access to their own swap files. If you do not have a local hard disk on which to store a permanent swap file, Novell recommends using a temporary swap file in your user subdirectory on the network. This will avoid conflicts between two users' permanent or temporary swap files. (Note: If you are running a shared version of Windows on the server, you should MAP drives to the network directories and not use the DOS SUBST command. This is unique to Windows 3.1. In all other applications, using the DOS SUBST command on a server in place of the NET MAP command is recommended). Interrupts VPICDA.386 is a patch written by Microsoft that fixes problems that arise when network boards are set to an interrupt of 2, 3, or 9 and above, for use with Windows 3.0. Microsoft states that you no longer need this patch with Windows 3.1. If you run across problems using these interrupts, check to see if you have a conflict with some other device using the same interrupt. Interrupt 2, being used by a machine with a VGA monitor, is the most common conflict that people run into. (See Fax Document 212 or FYI.P.6054 for information on resolving interrupt and I/O address conflicts.) Base I/O Addresses I/O addresses below 300 should not be used for network boards on machines that also use Windows. Changes to SYSTEM.INI Make sure that the following lines are in the [386Enh] section of the Windows SYSTEM.INI file: [386Enh] UniqueDOSPSP = ON PSPIncrement=5 TimerCriticalSection=10000 ReflectDOSInt2A=ON OverlappedIO=OFF If you do not have these options set, you will not be able to enter Windows if you have NetWare Lite loaded. You will be given a message that they need to be added and returned to the DOS prompt. The purpose of these changes is to enhance the compatibility between Windows and networks. Changes to WIN.INI There are several options you can set in the WIN.INI file for network control. NetWare Lite does not require using anything other than the default values for these options. Consult your Windows documentation for further information if you wish to change these options. Third-Party Disk Caches Some third-party disk caches do not work with NetWare Lite v1.1 or networks in general. If you have problems with Windows running slowly with your disk cache, you may want to shrink the size of memory allocated to the disk cache as explained in the section "DR DOS 6.0 Configuration Items," number 2, which discusses Super PCKwik. If you are using a disk cache other than the NetWare Lite NLCache, you will need to disable the advanced reads and writes, sometimes called delayed or deferred writes. To do this, you will need to refer to the documentation of your particular disk cache. If you have problems with corrupted files or lockups, you may want to remove your disk cache. There are some third-party caches, especially those that perform advanced reads and delayed writes, that have compatibility problems with NetWare Lite. If you have questions about what has been tested with NetWare Lite, check Fax Document 206 or FYI.P.6077, Application Compatibility List. Third Party Memory Managers If you have questions about your memory manager, you may want to check the section DR DOS 6.0 Configuration Items, numbers 3 and 4, which discuss EMM386.SYS, the memory manager that ships with DR DOS 6.0. Though the syntax of commands may be different, the items that you need to do are usually the same. You will need to refer to your documentation on your memory manager to decide the best format for those commands. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Converting High Density to Low - (NetWare Lite v1.0) DOCUMENT ID#: FYI.P.6078 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Converting High Density to Low (NetWare Lite v1.0) This document was created to help anyone who has NetWare Lite v1.0 on a single high density disk but needs it on two low density disks because of floppy drive limitations. The source code is the same for NetWare Lite sold on one 3 1/2 diskette as that sold on two 5 1/4 diskettes. If you have it on one 3 1/2 diskette, the only crucial part to converting it over to two 5 1/4 is placing the right files on the right diskette. The first diskette is called the PROGRAM diskette and must contain the following: CLIENT EXE 16102 09-11-91 7:11p INSTALL EXE 44032 09-11-91 7:11p NET EXE 29416 09-11-91 7:11p SERVER EXE 34310 09-12-91 7:11p NET HLP 95574 09-11-91 7:11p LITE$RUN OVL 2400 09-11-91 7:11p README TXT 32648 09-12-91 7:11p The second diskette is called the DRIVERS diskette and must contain the following: DRIVER LST 1221 09-11-91 7:11p WDPLUS COM 17076 06-21-91 2:11p 3C503 COM 14821 06-14-91 9:14a 3C523 COM 12238 07-29-91 9:35a IPXODI COM 20885 06-25-91 1:52p LSL COM 7557 06-25-91 1:42p NE1000 COM 12717 07-29-91 9:37a NE2 COM 13028 07-29-91 9:33a NE2000 COM 13018 06-03-91 1:25p NET OVL 87092 09-11-91 7:11p PCN2L COM 14117 07-17-91 3:40p TOKEN COM 15663 06-14-91 4:10p TRXNET COM 12128 08-06-91 10:48a DEDICATE COM 170 09-11-91 7:11p DEMO EXE 11766 09-11-91 7:11p NETBIOS EXE 21506 11-15-90 3:48p NLSNIPES EXE 18042 09-11-91 7:11p NE2000 INS 96 09-11-91 7:11p 3C503 INS 170 09-11-91 7:11p WDPLUS INS 219 09-11-91 7:11p NE1000 INS 97 09-11-91 7:11p TRXNET INS 203 09-11-91 7:11p After these files have been copied appropriately, place the program diskette in one of the floppy drives and type INSTALL. The install process will then continue as described in the manual. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing or Upgrading NetWare Lite v1.1 DOCUMENT ID#: FYI.P.6080 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Installing or Upgrading NetWare Lite v1.1 INSTALL NetWare LITE v1.1 Use these procedures when the workstation does not have a copy of NetWare Lite v1.0. If you install the same copy of NetWare Lite v1.1 on more than one computer on your network, the system displays a license violation error. For Server-only, Client-only, or Server-client Workstations Loading from a Hard Drive 1. Place the NetWare Lite v1.1 PROGRAM diskette into a disk drive. With the DOS prompt set to the disk drive, type INSTALL, and press <Enter>. 2. Follow the instructions on the screen. For Client-only Workstations Loading from a Client Diskette (Except those Loading from a Bootable 5.25-inch, Low-density Client Diskette) 1. Format a diskette (either bootable or nonbootable). 2. Place the NetWare Lite v1.1 PROGRAM diskette into a disk drive. With the DOS prompt set to the disk drive, type INSTALL, and press <Enter>. 3. Select "Make this machine a client." 4. When the "Install Client" form appears, change the "Target directory for CLIENT software" field to a disk drive letter, press <Enter>, and follow the instructions on the screen. Files are copied to memory and a prompt appears. 5. When prompted for the target diskette, insert the formatted diskette into the specified disk drive, press <Esc>, and follow the instructions on the screen. For Client-only Workstations Loading from a Bootable 5.25-inch, Low-density Client Diskette 1. Format a blank, nonbootable diskette. 2. Format a blank bootable diskette. 3. Place the NetWare Lite v1.1 PROGRAM diskette into a disk drive. With the DOS prompt set to the disk drive, type INSTALL and press <Enter>. 4. Select "Make this machine a client." 5. When the "Install Client" form appears, change the "Target directory for CLIENT software" field to the same disk drive that the PROGRAM diskette is in, press <Enter>, and follow the instructions on the screen. Files are copied to memory and a prompt appears. 6. When prompted for the target diskette, remove the PROGRAM diskette from the disk drive, insert the nonbootable diskette into the same disk drive, press <Esc>, and follow the instructions on the screen. 7. Delete NET.HLP from the nonbootable diskette. This removes the online help function but makes enough space to copy the files to a bootable diskette. 8. Copy the files from the nonbootable diskette to the bootable diskette. See your DOS documentation for copy instructions. 9. Boot the computer using the NetWare Lite v1.1 bootable client diskette. UPGRADE FROM NetWare LITE v1.0 to v1.1 Use the upgrade option to change a workstation's NetWare Lite v1.0 to v1.1. You can upgrade all computers on the network running NetWare Lite v1.0 to v1.1 with only one copy of NetWare Lite v1.1. Note: It is imperative that all machines with NetWare Lite v1.0 be upgraded to v1.1 at the same time. Under no circumstances should both versions be on the same Network simultaneously. For Server-only, Client-only, or Server-client Workstations Loading from a Hard Drive 1. Place the NetWare Lite v1.1 PROGRAM diskette into a disk drive. With the DOS prompt set to the disk drive, type INSTALL and press <Enter>. 2. Select "Upgrade this machine to v1.1." 3. Follow the instructions on the screen. For Client-only Workstations Loading from a Client Diskette (Except those Loading from a Bootable 5.25-inch, Low-density, Client Diskette) 1. Place the NetWare Lite v1.1 PROGRAM diskette into a disk drive. With the DOS prompt set to the disk drive, type INSTALL and press <Enter>. 2. Select "Upgrade this machine to v1.1." 3. When the "Type the directory path of NWLITE 1.0" prompt appears, type the disk drive letter and press <Enter>. Files are copied to memory and a prompt appears. 4. When prompted for the target diskette, insert the workstation's client diskette into the specified disk drive and press <Esc>. 5. Follow the instructions on the screen. For Client-only Workstations Loading from a Bootable 5.25-inch, Low-density, Client Diskette NetWare Lite v1.1 client software fits on a nonbootable 5.25-inch, low-density diskette, but it does not fit on a bootable diskette. 1. Format a blank, nonbootable diskette. 2. Copy the NetWare Lite v1.0 CLIENT.EXE from the original NetWare Lite v1.0 PROGRAM diskette or your NetWare Lite v1.0 client diskette to the nonbootable diskette. See your DOS documentation for copy instructions. 3. Place the NetWare Lite v1.1 PROGRAM diskette into a disk drive. With the DOS prompt set to the disk drive, type INSTALL and press <Enter>. 4. Select "Upgrade this machine to v1.1." 5. When the "Type the directory path of NWLITE 1.0" prompt appears, if your PROGRAM diskette is in drive A:, type A: and press <Enter>. If your PROGRAM diskette is in drive B:, type B: and press <Enter>. Files are copied to memory and a prompt appears. 6. When prompted for the target diskette, remove the PROGRAM diskette from the disk drive, insert the diskette with the copy of NetWare Lite v1.0 CLIENT.EXE on it into the same drive and press <Esc>. 7. After CLIENT.EXE is upgraded and the other files are copied to the diskette, delete NET.HLP. This removes the online help function, but makes enough space to copy the files to a bootable diskette. 8. Copy the files from the nonbootable diskette to your NetWare Lite v1.0 bootable client diskette. See your DOS documentation for copy instructions. 9. Reboot the computer using the NetWare Lite v1.0 bootable client diskette. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Converting High Density to Low (NetWare Lite v1.1) DOCUMENT ID#: FYI.P.6081 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Converting High Density to Low (NetWare Lite v1.1) This document is for those who have one high density diskette and need assistance converting and transferring files to two low density diskettes. The following is a list of the files needing to be placed on each diskette. First diskette must be labeled PROGRAM and contain the following files: NE2000 INS 96 9-11-91 7:11p 3C503 INS 170 9-11-91 7:11p WDPLUS INS 219 9-11-91 7:11p NE1000 INS 97 9-11-91 7:11p TRXNET INS 203 9-11-91 7:11p LITE$RUN OVL 2400 9-11-91 7:11p NET EXE 35368 5-28-92 4:05p TBMI CO@ 4615 7-10-91 12:27p TBMI2 CO@ 5062 12-04-91 2:46p DRIVER LST 1556 4-01-92 11:24p SERVER EXE 45411 7-01-92 8:25a NET HL@ 17492 5-18-92 3:41p NET OVL 95685 6-16-92 1:47p NE1500T INS 127 3-23-92 8:44a NE2100 INS 126 3-23-92 8:43a INSTALL EXE 59754 6-30-92 8:29a CLIENT EXE 21081 6-29-92 4:40p The second diskette must be labeled DRIVER and contain the following files: 3C503 CO@ 8574 6-14-91 9:14a 3C523 CO@ 7604 7-29-91 9:35a DEDICATE COM 192 3-10-92 9:31a NE1000 CO@ 7889 7-29-91 9:37a NE1500T CO@ 8038 10-11-91 5:09p NE2 CO@ 9283 11-04-91 4:19p NE2000 CO@ 8181 6-03-91 1:25p NE2100 CO@ 8034 10-11-91 5:10p NETBIOS EX@ 12653 5-18-92 3:26p IPXODI CO@ 12252 11-20-91 4:57p NLCACHEM EX@ 2362 5-05-92 12:47p NLCACHEX EX@ 13873 5-05-92 12:47p NLCACHEC EX@ 10706 5-05-92 12:46p NLSNIPES EXE 18042 9-11-91 7:11p LSL CO@ 6031 1-30-92 4:05p PCN2L CO@ 8746 7-17-91 3:40p IPXSYNC EXE 15664 7-01-92 11:44a WDPLUS CO@ 10902 6-21-91 2:11p README TXT 54345 7-06-92 11:14a TASKID CO@ 1681 12-19-90 3:48p UPATCH EXE 19690 1-16-92 9:35a CACHE TX@ 9753 6-01-92 5:26p VIPX 38@ 7501 7-08-92 10:55a TOKEN CO@ 10242 6-14-91 4:10p TRXNET CO@ 7696 8-06-91 10:48a NLCINST EX@ 24542 6-02-92 8:13a SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: CD-ROM drive DOCUMENT ID#: FYI.P.6084 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM CD-ROM drive The following describes configuring your system to run with NetWare Lite and a CD-ROM drive: MSCDEX.EXE, the program provided from Microsoft to run a CD-ROM, assigns a drive letter to the CD-ROM drive. This can default to the next available drive, or can be set to a specific drive with the /L:x parameter, where x is the drive letter. However, there are conflicts between MSCDEX.EXE and CLIENT.EXE, a NetWare Lite file that is loaded to make the machine a workstation. A workaround some of these conflicts is the following: PREFERRED METHOD 1. Load CLIENT.EXE then run MSCDEX.EXE SECONDARY METHOD This has been known to solve some but not necessarily all CD-ROM drive and NetWare Lite issues. If PREFERRED METHOD fails and the workstation was a CLIENT-only, it must be made a SERVER-CLIENT. 1. Run MSCDEX.EXE before CLIENT.EXE. This will assign a drive letter to the CD-ROM. 2. After running CLIENT.EXE, that drive letter is no longer directly accessible by DOS. Create a network directory that looks at the drive through the network. For example, if the /L:G parameter was used in MSCDEX to assign the G: drive to the CD-ROM drive, then create a network directory (Enter NET; select SUPERVISE THE NETWORK; select NETWORK DIRECTORIES; press <Insert>; select your SERVER), call it something like CDROM, and assign the "Actual directory path" to be the G: drive. 3. Then, when you map a drive to the network directory CDROM, even though the G: drive is not accessible directly, you can access it as a mapped drive. For example: NET MAP J: CDROM would map J: to the CDROM network directory that will look at the physical drive G: that MSCDEX.EXE assigned as the CD-ROM drive. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NE2000 Jumper Settings DOCUMENT ID#: FYI.P.6096 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NE2000 Jumper Settings This document is for the NE2000 network board only. Due to the frequent success, use, and popularity of this network board, Novell is providing the following information in case the original documentation is misplaced or otherwise unavailable. When doing a first time installation or needing to change any settings to avoid conflicting with other hardware, use this handy chart. ┌────────────────────────────────────────────────────────────── ─────────┐ │ Set interrupt line (IRQ), use jumper block labeled W12, W13, W14, W15.│ │ │ │ Interrupt (IRQ) Jumper blocks │ │ Line W12 W13 W14 W15 │ │ 2 ON OFF OFF OFF │ │ 3 OFF ON OFF OFF │ │ 4 OFF OFF ON OFF │ │ 5 OFF OFF OFF ON │ │ │ │ Set base I/O address, use jumper blocks W9, W10, W11. │ │ │ │ Jumper blocks │ │ Port Address W9 W10 W11 │ │ 300 ON ON *** │ │ 320 OFF ON *** │ │ 340 ON OFF *** │ │ 360 OFF OFF *** │ │ ***May leave unchanged. │ │ │ │ Note: W11 jumper is not used for base I/O address or interrupt line │ │ settings but is included as part of the W9-W11 block. Its │ │ purpose is for remote boot capability that at this time is not │ │ supported by NetWare Lite. │ └────────────────────────────────────────────────────────────── ─────────┘ Connector Type To select the connector type, use jumpers W1-W8. The selection of this connector type depends on the use of thin Ethernet cable (BNC connector) or thick Ethernet cable (DIX connector), sometimes referred to as twisted pair connection depending on cable hardware. The bottom is referring to the edge of the network board with the gold fingers that insert into the system-board expansion slot. Jumpers W1-W8 have three pins each. The bottom two rows must be jumpered for BNC connector type (This is a default setting). For DIX connector type, jumper the top two rows. Notice, the physical location of jumpers will correspond to the location of the connectors at the end of the network board. W16 jumper This jumper sits all by itself and helps to resolve some timing issues. With some machines using Chips and Technologies chipset there is a slight bus-timing difference. Microcode for the NE2000 was modified to help compensate for the timing problem dependent on whether W16 is jumpered or not. This has not been documented as a problem with NetWare Lite. However, if you suspect a timing problem and have the fore mentioned chipset, remove jumper from W16. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ACCPAC DOCUMENT ID#: FYI.P.6053 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Installing ACCPAC General Information 1. Follow the installation instructions for NetWare Lite v1.0 carefully. Download Fax document 235 or FYI.P.6050 for help with installing and setting up a network. 2. The installation procedures will create a \NWLITE directory on your C:\ drive. You need to edit a file called STARTNET.BAT that is located in this directory. 3. Look for the line in STARTNET.BAT that loads the program called SHARE. If you are using MSDOS, change that line to the following: C:\DOS\SHARE /L:250 /F:10000 If you are using DR DOS, change the line to the following, instead: C:\DRDOS\SHARE /L:250 4. The "FILES=" parameter in your CONFIG.SYS should be set as follows on both the workstations and the server: FILES=250 5. Obtain the patches that Novell has released for NetWare Lite v1.0. Please acquire Fax Document 263 or see FYI.P.6087 for more information. Installing Windowing System Manager and LANPak (Much of the following information was obtained from Computer Associates Limited. A similar document is found on their fax system.) 1. Insert WSM DISK 1 in drive A: and type A:INSTALL from the root directory to which you are installing. Answer "yes" to indicate that you are installing on a network. You will be prompted for additional disks. 2. Upon completion of the WSM install, you will be taken to the "Install Programs" portion of WSM, at which point you should insert the LANPak disk and continue. 3. When the system prompts you if you are installing on Novell NetWare, answer NO. This is not Novell NetWare. NetWare Lite is a peer-to-peer network that means that it is DOS-based--quite different from NetWare 2.x and 3.x. 4. Choose "PC-Lan," or if you wish, choose "other," and type NETWARE LITE. The preceding is the most critical step. If you have already installed the LANPak as Novell, you are probably suffering a great deal of "Unable to obtain access to...." messages. Just reinstall the LANPak as above. 5. Continue with the application installation. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Official Books List DOCUMENT ID#: FYI.P.6098 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Official Books List The following is a list of official books generated by NOVELL PRESS, published by SYBEX concerning both NetWare Lite and DR DOS. Novell acknowledges other publications available at major bookstores but regrets that they are not able to be included in this listing. Due to various rights to publishing information, Novell can only suggest that if you are interested in further publications to consult your local bookstore. Other OFFICIAL NOVELL publications will be listed as they become available. The Official Novell NetWare Lite Handbook by Ed Liebing Published by SYBEX ISBN 0-7821-1095-9 This book is a complete guide for NetWare Lite v1.0 and v1.1. It covers installation, maintenance, and troubleshooting. If you are a NetWare Lite novice, it will introduce you to NetWare Lite and networking. It contains a troubleshooting guide and provides solutions to most common problems. The Official Novell DR DOS 6 Instant Reference by Robert M. Thomas Published by SYBEX ISBN 0-7821-1094-0 This book covers every feature and command in an easy to use, alphabetical order. It provides examples, useful tips, and pointers. If you are new to DR DOS, it will help in installing, configuring, and optimizing your system. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: TSRs and NetWare Lite DOCUMENT ID#: FYI.P.6112 DATE: 18DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM TSRs and NetWare Lite TSR (Terminate and Stay Resident) NetWare Lite is designed around two primary TSRs. 1. SERVER.EXE, that acts as the "disperser" of requests whether it be printing or file services. SERVER.EXE is quite complex and considers several issues particularly background printing, DOS/Windows busy flags, file sharing (through Share), and communication with other servers/clients on the network. 2. CLIENT.EXE acts as the redirector if the request is not for DOS. Because both SERVER.EXE and CLIENT.EXE execute as a TSR on DOS, it is necessary to hook interrupts to provide the functionality for NetWare Lite. Typically, problems will be met when two or more TSRs attempt to hook an interrupt and may not be aware of the other TSR hooking that interrupt. This, in essence, is usually the cause of TSRs not coexisting with one another. In a peer-to-peer network such as NetWare Lite the issue is greatly magnified due to functionality requirements that a peer-to-peer LAN provides. Novell, has not done a comprehensive test matrix regarding compatibility with other TSRs and NetWare Lite. However, it is recommended that the TSR vendor be contacted for compatibility with NetWare Lite v1.1 if problems are met. TSRs Known to Have Problems 1. Pyro (screen saver) Symptoms: Locks other stations when it activates. 2. PC Support Program (3270,5250 emulation) Symptoms: Locks other stations and causes printing not to work. Note: Other resident applications such as ViewMax (with DR DOS), and DESQview may exhibit similar problems. Suggested Workaround If problems are met and several applications or TSRs are being loaded, you may consider the following suggestions: 1. TSRs come in many forms such as, virus checking, screen savers, cache drivers, mouse drivers, or hotkey (popup) type applications. A. First remove TSRs one at a time until a possible culprit is identified. B. Try rearranging the load order of other TSRs and NetWare Lite. C. If using Windows, check to see if TSRs are loaded before Windows or from Windows using an icon or if loading from a DOS box. Depending on which method is used, you may try changing the load order or method. 2. If memory management is being used, check to see where TSRs are loading. Sometimes a larger TSR may not have enough Upper memory available and will load into conventional memory. This may be undesirable if it uses to much conventional memory. You may try loading different TSRs to Upper or Conventional memory to see what works best for you. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Removing a Server DOCUMENT ID#: FYI.P.6051 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6035 SYMPTOM NA ISSUE/PROBLEM Removing a Server If you set up your machine as a server and want to remove the server software from your hard drive, complete the following: 1. Boot your machine without loading SERVER. 2. Run the original INSTALL.EXE that came on the installation diskettes. 3. Select "Make this machine a client." When asked to select the network board, press <Esc> and exit the INSTALL utility. The server is now removed from your hard disk drive. Another option is simply to remove SERVER.EXE from your STARTNET.BAT file. This way, SERVER.EXE will not be loaded; hence, the machine will be a client only. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Loading CLIENT and SERVER into Upper Memory DOCUMENT ID#: FYI.P.6007 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Loading CLIENT and SERVER into Upper Memory Memory managers that load terminate-stay-resident (TSR) programs such as CLIENT.EXE and SERVER.EXE into upper memory reserve a fixed length block of memory to load the program. As long as the program is the same size in memory as it is on disk, there will be no memory conflict. However, SERVER.EXE is actually larger when it is loaded than it is on disk. Because SERVER.EXE is larger, memory managers that do not account for such growth may load SERVER into too small of a memory block. This can cause memory corruption and the computer to hang. To avoid this type of problem, Novell suggests that you do not load SERVER into upper memory. CLIENT does not grow when loaded so it can be loaded "high." SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DOS Memory Managers and NetWare Lite v1.1 DOCUMENT ID#: FYI.P.6101 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM DOS Memory Managers and NetWare Lite v1.1 Note: Information listed is intended for use on 386 or 486 based computers. For information on other machines, please consult your DOS manual. This document is intended to aid the user in the basic steps of loading NetWare Lite items into upper memory. General Information This basic summary is necessary to understand how to create the best performing servers and clients with NetWare Lite. Random Access Memory (RAM) in 386 and 486 computers has a uniform structure. The first 640 KB of memory is known as conventional memory, the location where applications load. The next 384 KB of memory is known as upper memory, where system files and other files (such as mouse drivers or network drivers) can be loaded if memory management software is used. On machines with more than 1 MB of RAM, the first 64 KB of memory above 1 MB is known as the HMA (High Memory Area). All the necessary files in NetWare Lite v1.1 may be loaded into upper memory. These files are normally loaded from the STARTNET.BAT file found in the NWLITE directory. These files are: LSL.COM, your network board driver (NE2000.COM), IPXODI A, SHARE (found in your DOS directory), SERVER.EXE, and CLIENT.EXE. The proper syntax for loading these files into upper memory depends on which version of DOS and memory manager you choose to use. Following are instructions to load NetWare Lite files into upper memory by using memory managers from DR DOS 6.0 and MS-DOS 5.0. If you have any questions that are not answered in this document, please consult your DOS documentation. The memory manager, EMM386, will relocate software into upper memory. Without the use of the EMM386 manager, the only memory that can be used is conventional memory (the first 640 KB of memory). DR DOS 6.0 The memory manager included with DR DOS 6.0 is EMM386.SYS. To load drivers and programs into upper memory, several steps must be followed. Note: EMM386.SYS cannot be used with other memory managers. The following is an example of a CONFIG.SYS file that is configured to allow access to upper memory (UMB) and HMA. HIDOS=ON DEVICE=C:\DRDOS\EMM386.SYS /F=AUTO /K=AUTO /B=FFFF /R=AUTO /E=[START-END] HIDOS=ON In the CONFIG.SYS file, the HIDOS=ON line should be included. This allows the computer to put information into HMA if memory is available. EMM386.SYS [/F=AUTO] Performs an automatic search through upper memory for a free 64 KB window. This is the default. This sets up your machine to use either expanded or extended memory, whatever your software requests. NetWare Lite will not be able to load completely into upper memory if this option is used because of limited space. Novell suggests if possible you use [/F=NONE] that will set your machine up to use extended memory and free up considerably more upper memory. [/K=AUTO] Allocates expanded memory. The amount of memory is determined by how much your application requests. [/B=FFFF] Relocates the DR DOS kernel, freeing space in conventional memory for use by applications. By using the ffff location of memory, the kernel will be placed into HMA (if available). [/R=AUTO] Copies data and code from Read Only Memory (ROM) that is slow to run into Random Access Memory (RAM) that is very fast. [/E=[START-END] Excludes an area of upper memory from the area being checked for availability of use. This switch should be used if an item uses a specific memory location. For example: If your network board had a memory address setting of CC00 and you used the switch [/E=CC00-CFFF], then the EMM386.SYS driver would not allow any software to occupy the same area of memory. This is a solution to random errors (the machine lockup) that may occur if the network-board driver is overwritten. To load NetWare Lite required files into high memory in your STARTNET.BAT file, your syntax should be similar to the following: HILOAD LSL HILOAD NE2000 HILOAD IPXODI A HILOAD SHARE HILOAD SERVER HILOAD CLIENT To examine where your items are loaded into high memory, type the following from the DOS prompt: MEM /A /P (/A shows all information. /P pauses at the end of every screen.) From this screen you will be given several screens of information. To determine what is located in upper memory, be aware that the address A000:0000 is where conventional memory ends and upper memory begins, and FFFF:0000 is where upper memory ends and the high memory area begins. For complete information on the MEM command, please refer to page 258 to 259 of the DR DOS 6.0 User's Guide or call the DRI Automated Fax system at 1-408-649-2344. The titles pertaining to memory management are the following: Document Title 1000 Master Index (A Complete Listing of all Files on the DR DOS Fax System.) 1300 DR DOS 6 Memory Management overview 1301 Basic Memory optimization 1302 Trouble shooting 1303 Using Third-party memory managers 1305 XMS-EMS memory pool 1306 Preventing DR DOS from loading into HMA 1307 The MEM /A Command 1308 Gate A20 and Printing Problems MS-DOS 5.0 The memory manager included with MS-DOS 5.0 is EMM386.EXE. To load drivers and programs into upper memory, several steps must be followed. In the CONFIG.SYS file, device drivers for HIMEM.SYS and EMM386.EXE must be included and placed in a specific order. To ensure the proper setup, it is best to have the device line containing HIMEM.SYS at the beginning of the CONFIG.SYS file, the second line should contain the EMM386.EXE line, and the third line should contain a specification of where to load the DOS system files. For example: DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE /X=MMMM-NNNN NOEMS DOS=HIGH,UMB HIMEM.SYS Generally, the default specifications for HIMEM.SYS are sufficient for your system. The main exception is the /MACHINE:XXXX specification; replace XXXX with your machine type. Please see page 611 in the MS-DOS 5.0 User's Guide for complete information. EMM386.EXE Switches included with EMM386.EXE that are most commonly used to increase system performance are the following: [X=[MMMM-NNNN]] Where MMMM-NNNN denotes an address that EMM386.EXE will not be allowed to use. This is very useful for excluding the address of your network-board driver so it will not be overwritten by DOS. (If the board memory address is set at CC00, the switch would be X=CC00-CFFF.) [NOEMS] Allows access to upper memory and prevents access to expanded memory. It does allow access to extended memory. Other switches can be found in the MS-DOS 5.0 User's Guide on pages 605 to 609. DOS The HIGH switch allows DOS to relocate the system files into a location called the HMA (High Memory Area), freeing up more conventional memory space. The UMB (Upper Memory Block) switch is for linking conventional memory with upper memory. Loading drivers or devices into upper memory is necessary. Remember, to load any command high, the line must follow the three lines listed above. The command to load a device high in the CONFIG.SYS file is DEVICEHIGH. The command to load an item high in the AUTOEXEC.BAT file or any .BAT file is LH or LOADHIGH. To load the required NetWare Lite files into high memory in your STARTNET.BAT file, your syntax should be similar to the following: LH LSL LH NE2000 LH IPXODI A LH SHARE LH SERVER LH CLIENT To examine where your items are loaded into high memory, type the following from the DOS prompt: MEM /C |MORE (/C classifies programs by memory usage. It also displays conventional memory and upper memory in separate blocks to easily determine where programs are loaded . |MORE pauses at the end of every screen.) For further questions and concerns about loading software into upper memory, consult the MS-DOS 5.0 User's Guide or contact Microsoft Technical Support. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Top Support Issues DOCUMENT ID#: FYI.P.6085 DATE: 03DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6051 SYMPTOM NA ISSUE/PROBLEM Top Support Issues SHARE.EXE: Status Report 5 When loading SERVER.EXE, you may get a "Status Report 5" message that means that SHARE.EXE has not been loaded. SHARE.EXE is a program that comes with DOS 3.1 or above. SHARE is the mechanism that allows files to be accessed simultaneously from multiple clients. If you get a "Status Report 5" message, you either do not have SHARE.EXE in your PATH or you do not load it anywhere before SERVER.EXE is loaded. Add the appropriate directory to your PATH (where SHARE.EXE is located) or copy SHARE.EXE to the directory where NetWare Lite is installed. Although loading SHARE is not required for the server to run, it is strongly recommended. SHARE should be loaded before SERVER. SHARE should be tuned for proper performance. You may need to increase the values for locks (/L) and files (/F) if you run database applications or if you have more than four users accessing the server. See your DOS documentation for more information on configuring SHARE. You do not need to load SHARE before loading CLIENT. See Fax Document 111 or FYI.P.6003 for more information. Setting LASTDRIVE LASTDRIVE is a DOS command that is executed at boot time from the CONFIG.SYS file. The NetWare Lite NET utility uses LASTDRIVE to identify valid drives and to provide compatibility with other NetWare products. The installation programs default value of LASTDRIVE=M: should work for most situations. If you wish to use a value other than M:, be aware that LASTDRIVE should be set to G: or greater for NET to run. LASTDRIVE is set by including a command such as "LASTDRIVE=G:" in CONFIG.SYS. If you attempt to run NET with LASTDRIVE set lower than the G: drive or not set, you will have to increase the value of LASTDRIVE and reboot before any NET command can be executed. The IPXODI Driver The IPX shipped with NetWare Lite (IPXODI) is not new and is not special to NetWare Lite. Novell has made a general decision to convert from linked IPX to IPXODI. IPXODI is shipped with the LAN Workplace for DOS product and with DOS/Windows shell kit. IPXODI is functionally identical to the linked version of IPX, although the LSL offers multiple-protocol and MLID capabilities. NetWare Lite can be run on top of either (but not both) linked IPX or IPXODI. STARTNET.BAT, which is created as part of the NetWare Lite installation, should be modified not to load LSL (the ODI driver) and IPXODI if linked IPX is already being loaded elsewhere (like in your AUTOEXEC.BAT). See Fax document 118 or FYI.P.6006 for more information. Loading CLIENT and SERVER into Upper Memory Memory managers that load terminate-stay-resident (TSR) programs such as CLIENT.EXE and SERVER.EXE into upper memory reserve a fixed length block of memory to load the program into. As long as the program is the same size in memory as it is on disk, there will be no memory conflict. However, SERVER.EXE is larger when it is loaded into memory than it is on disk. Because SERVER.EXE is larger, memory managers that do not account for such growth may load SERVER into too small of a memory block. This can cause memory corruption or can cause the computer to hang. To avoid this type of problem, do not load SERVER into upper memory. CLIENT does not grow when loaded, so it can be loaded "high." Please see Fax Document 119 or FYI.P.6007 for more information. Windows Some NetWare Lite users have had trouble getting Windows 3.0 to run smoothly with NetWare Lite. Fax Document 210 or FYI.P.6044 gives some hints how to configure both NetWare Lite and Windows 3.0 to gain better performance. All Windows/NetWare Lite users should download this document. Network Applications Installing applications on NetWare Lite may be different from installing applications on NetWare. NetWare is, as you know, a very popular LAN. Many applications have NetWare specific installation options. These installation options do not apply to NetWare Lite networks. NetWare Lite is a DOS peer-to-peer network. If the application being installed has network specific installations, then "Other networks.." or "DOS peer-to-peer network" or similar networks should be selected. Do not select NetWare or Novell installation options. See Appendix B in the NetWare Lite documentation for more details about using NetWare Lite with NetWare. Please see Fax document 211 or FYI.P.6011 for more information. Connections Many of the problems that NetWare Lite technical support deals with are related to network connections. Connection problems become the culprits that cause many other seemingly unsolvable problems. Most of these connection problems are caused by things such as bad or misconfigured hardware, drivers, or memory managers. Fax Document 215 or FYI.P.6094 explains how to troubleshoot and overcome connection problems. Installing "Other" Network Board Drivers When loading NetWare Lite, you are prompted to select a network-board driver. Unfortunately, the installation program fails to complete properly if "other" is selected. If you need to use a board driver not supplied on the original installation diskettes, you can avoid this problem by making a backup copy of the original diskettes and copying the board driver to this backup. Use the new diskette to install NetWare Lite. Note: If you make a separate backup of the "driver" diskette you must copy your board driver to the "driver" backup. See Fax Document 217 or FYI.P.6091 for a step-by-step procedure on how to do this. Network Setup Fax document 235 or FYI.P.6050 gives the user tips on how to configure the network. It explains mappings, captures, and network resources. It also goes through an example of a network configuration. Patches Novell has released several patches that should be applied by NetWare Lite users who have problems that they are unable to solve. Please see Fax Document 263 or FYI.P.6087 for more information on how to get the patches and what problems they solve. Resolving I/O and IRQ Conflicts Fax Document 212 or FYI.P.6054 gives a list of possible conflicts in hardware setup. Network board and other devices may have conflicting I/O addresses or interrupts. This list may clarify some of the problems. NetWare Lite v1.1 and Windows 3.1 Compatibility This is a lengthy document similar to Fax Document 205 or FYI.P.6061. It does contain more concise information concerning Windows 3.1 and particularly using it with NetWare Lite v1.1. It will take you through different install methods and options depending on DOS versions being used. For details, see Fax Document 206 or FYI.P.6077. Trouble Shooting Lockup (Hanging) Problems Installing a Network system may be challenging particularly if a lockup is met. Several things may cause this (Fax document 218 or FYI.P.6086 gives ideas to help diagnose such problems). It explains hardware or switch setting conflicts, memory conflicts, bad hardware, software conflicts or the need of configuration changes. DOS Memory Managers and NetWare Lite v1.x This is a summary to help create the best performing servers and clients and how to use memory. Inclusive is how to load NetWare Lite files into upper memory. This document includes the use of memory managers and different DOS commands for such. See Fax document 264 or FYI.P.6076 for details. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Setting LASTDRIVE DOCUMENT ID#: FYI.P.6005 DATE: 01OCT92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Setting LASTDRIVE LASTDRIVE is a DOS command that is executed at boot time from the CONFIG.SYS file. The NetWare Lite NET utility uses LASTDRIVE to identify valid drives and provide compatibility with other NetWare products. The installation programs default value of LASTDRIVE=M: should work for most situations. If you wish to use a value other than M:, be aware that LASTDRIVE should be set to G: or greater for NET to run. LASTDRIVE is set by including a command such as "LASTDRIVE=G:" in CONFIG.SYS. If you attempt to run NET with LASTDRIVE set lower than the G: drive or not set, you will have to increase the value of LASTDRIVE and reboot before any NET command can be executed. When LASTDRIVE is set to the F: drive, network directories can be mapped to any drive letter up to LASTDRIVE (except C: if SERVER is loaded). However, the F: drive must be mapped to map D: or E: drive. If the situation occurs where the D: or E: drive is mapped and the F: drive is not mapped, the LASTDRIVE error message will result upon execution of the next NET command. To avoid this problem set LASTDRIVE to the G: drive or greater. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: How to Configure a NetWare Lite Server v1.1 DOCUMENT ID#: FYI.P.6103 DATE: 04DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6060 SYMPTOM NA ISSUE/PROBLEM How to Configure a NetWare Lite Server v1.1 The purpose of this document is to explain the server statistics that are configurable within NetWare Lite. These server statistics can be viewed and changed in the Net utility. To access the configuration menus, perform the following steps after logging in to the network: 1. From the c:> prompt, type NET. 2. Select "Supervise the network." 3. Select "Server configuration." 4. Select the server to view. SERVER CONFIGURATION SCREEN The following is an example of the server configuration screen with default settings: Configuration Information for Server NetWare Lite CFG FUTURE Connections (2-25) 4 4 Client tasks (4-200) 10 10 Network directories (2-20) 4 4 Network printers (0-3) 1 1 Print buffer size (512-4096) 512 512 Number of receive buffers (3-20) 6 6 Receive buffer size (512-8192) 1024 1024 Number of IO buffers (0-25) 1 1 IO buffer size multiplier (2-64) 4 4 Future server memory size (approx.) 44,397 Allow remote management (Y/N) Y Y Future server name: NWLITE CFG and FUTURE Columns There are two columns of statistics on the right of this table labeled CFG and FUTURE. The CFG column indicates the settings that are currently being used. The FUTURE column is used to determine the network settings to be implemented the next time the network is started. If you want to make a change, make it in the FUTURE column and then reboot that server. After the server is rebooted, the new settings will be in effect and will appear in the CFG column. Configuration Settings Each item in the menu will be discussed in some detail. After each item is described, configuration information will be given to help correctly configure each item. CONNECTIONS Every computer on the network (client or server or both) has a connection table. This table keeps track of the number of connections that the computer has with other computers. Users are not able to view this table; however, the number of connections can be limited on a server. A connection is established when one computer accesses another computer across the network. For example, a connection is established if a client accesses a network resource, such as a network directory or network printer, located on a server. Server Connection Table A server's connection table contains a list of the node addresses of every client computer accessing printers or network directories on that server. Because the connection is actually the node address of the network board, only one connection is established per machine, regardless of how many drives a computer has mapped or how many printers a client machine is captured to. It is not possible for the number of connections in the server-connection table to be greater than the total number of clients on the network. When a server receives a request to map a drive, for example, it will look down the list of existing connections and will create a new connection only if the address of the requesting computer is not already on the list. Temporary Connections Temporary connections are occasionally established by the NET utility to do functions such as modify a user account, change a server's configuration. After the net utility has finished using the temporary connection, the connection is cancelled. Setting Connections Set the number of connections for each server by considering how many clients might be mapped or captured to the server at one time and add one to that number to provide for any temporary connections. Each connection in the Server's configuration menu uses approximately 80 bytes of memory. CLIENT TASKS Client tasks are the number of programs permitted to open files on a server. Each time a program on a client uses a resource on a server (such as starting a program), one client task is registered in a table on the server. This is the case whether the client loads the program from the server or whether it loads it from its own hard drive. If the same program opens more than one file, only one client task is still registered because client tasks refer to the number of programs that are opening files and not the number of files that are open on the server. On the other hand, if two different programs on a client open files on a server, then two client tasks are recorded in the table. Some programs call other programs that use server resources. When this happens, client tasks will increase by more than one when the program is initially started. A variety of problems are associated with not having enough client tasks. Usually errors will be displayed by the application that is currently running. Occasionally, the whole network will hang. Client Task Configuration Information The number of client tasks defaults to 10. A good rule of thumb is to set the number of client tasks to 10 per machine connected to the server (For example, If five machines have drives mapped to a server, set the client tasks on the server to 50). This should provide enough client tasks to operate the network. Approximately 100 bytes of memory are reserved on a server per each client task. Check the server status screen frequently to verify that you have enough client tasks. If you see the PEAK number of tasks in the server status screen approaching the CFG number (within 6), you should increase the number of client tasks to avoid problems. The CFG number should always be at least six higher than the PEAK number. Proper configuration of the number of client tasks on a server is especially important under the following conditions: ■ When running Microsoft Windows ■ When using a disk intensive program (a database program) ■ When supporting many clients Network Directories A network directory is a directory on a server that can be accessed by clients on the network. Increasing the number of network directories on a server allows more of its directories to be accessed by users across the network. Network Directory Configuration Information Set the number of network directories to as many as needed (up to 20). Network Printers This figure designates the maximum number of network printers allowed on a server. NetWare Lite will support up to three printers per server. A printer on a server does not necessarily have to be designated as a network resource. It can be run locally if SERVER.EXE is not loaded into memory. Each network printer defined takes up approximately 884 bytes of memory on the server. Network Printer Configuration This number should correspond to the number of printers physically connected to the server and defined as network resources. The maximum number of network printers per server is three. PRINT BUFFER Print Buffer Size NetWare Lite uses a print buffer to temporarily store information before it is printed. A print job follows the following path to the printer: Application -- DOS -- Client -- || network || -- Server -- Printer When someone prints a job from a client machine to a network printer, the information first goes to DOS. After interpreting that the printer port (LPT1 for example) has been captured to a network printer, DOS sends the print job to the network software on the client machine. The print job is sent across the network cabling to the computer with the printer attached and then taken by the server software and spooled to a directory on the hard drive. The path to where the data is being spooled is C:\NWLITE\NLCNTL \SLPT1. The NLCNTL subdirectory is a hidden directory and the SLPT1 directory corresponds to the printer port captured on LPT1. (If LPT2 was captured, the last subdirectory would be \SLPT2.) The job is spooled as a file then is loaded to an area in memory called the print buffer. From the print buffer, the print job is sent to the printer. The print buffer speeds up the printing, because accessing memory is much faster than accessing a hard disk drive. A large print buffer accesses information from the relatively slow hard drive fewer times and causes faster printing. Print Buffer Configuration Set the print buffer size to the maximum allowed value, unless limited memory is available. RECEIVE BUFFERS Number of Receive Buffers Each NetWare Lite server has two types of buffers related to overall network communication, which can be configured by a supervisor. They are the receive and IO buffers. Understanding receive and IO buffers and how to configure them requires an understanding of some basic NetWare Lite network communication concepts. When an application makes a request of DOS, such as reading data from a file or writing data to a file, DOS determines whether it can handle the request itself. If the requested operation involves a network resource, such as listing a network directory, DOS passes the request to the network that fills the request and gives the response back to DOS. Then, DOS passes the response back to the application. Each network request passes through four different stages before being sent out on the network cabling. The network provides information to DOS (such as which drives are actually network drives) so that DOS interprets when to pass requests to the network and when to return errors to the requesting application. Three programs provide the interface to the network hardware. They are the Internetwork Packet Exchange Protocol (IPX) driver (IPXODI.COM), the Link Support Layer (LSL) driver (LSL.COM), and the network-board driver (such as NE2000.COM). These three programs take requests from the network level and transform them into packets that are then sent out on the cable. When a packet is received at the server, SERVER.EXE is notified and the packet is placed in a free receive buffer. The server processes the request and then does one of two following action: If the requested operation is a disk read, the server reads the requested amount of data and places the response in a free IO buffer. If the request is for anything else, the server places the response back in the receive buffer where it got the request. The data is then transferred back across the network to the application that originally made the request. Number of Receive Buffers Configuration Information Set the number of receive buffers to three more than the number of clients that will be simultaneously accessing the server. The extra receive buffers are important. The server may be servicing requests from every client on the network and still needs extra buffers to listen for additional incoming requests. Even though all client machines may have requests pending at the server, a client may resend a request and the server needs extra buffers to handle any extra packets from the clients. Receive Buffer Size Description and Configuration Information The network is limited to the type of network hardware that is being used. A receive buffer cannot be set to anything larger than the packet size of a particular type of board. Typically Ethernet is limited to a packet size of 1450 bytes and ARCnet and Token-Ring are capable of sending and receiving 4096 byte packets, the limit of NetWare Lite. DOS reads information best in 512 byte increments, so receive buffers should be set to a multiple of 512 bytes even if the packet size is larger than the 512 byte multiple. For example, when using Ethernet boards, set the buffer size to 1024 bytes rather than the maximum allowed 1450 bytes because 1024 is an increment of 512, and the 1024 setting will be faster than 1450 bytes. IO BUFFERS Number of IO Buffers When a client makes a request, in responding to that request, the server fills the IO buffers with blocks of data to be sent across the cable for the next portion of that request. Number of IO Buffers Configuration Information The preferable setting for the number of IO buffers is one per client. Otherwise, set the number of IO buffers to one per every four receive buffers to save memory. Do not set the IO buffers greater than the number of clients that will be accessing the server. IO Buffer Size Multiplier and Configuration Information The IO buffer size multiplier indicates the size, in kilobytes, of each IO buffer. The guideline for setting the IO buffer size multiplier varies depending on the size that you would like your IO buffers to be. If memory is not a consideration, then set the buffer size multiplier high. That will allow more blocks of data to be stored in the IO buffer so that less disk reads are necessary. However, if memory is a consideration a smaller buffer size would be recommended. For every IO buffer, the server size will increase the amount of kilobytes that was specified for the multiplier. For example, if there are three IO buffers and the multiplier is 4, the server will increase in size by 12 KB. REMOTE MANAGEMENT Allow Remote Management If remote management is enabled, a network supervisor will be able to change a server's configuration settings from any machine on the network. If remote management is disabled, a server's configuration settings will only be able to be modified at the keyboard of the server itself. Note: Remote Management does not refer to modem use. Remote Management Configuration Enable or disable remote management depending upon the conditions in which the network is running. If security is a concern, remote management may need to be disabled. FUTURE SERVER NAME Future Server Name The future server name is the name that the server will be called the next time the network is started. SERVER STATUS SCREEN Status Information for Server NetWare Lite Server up-time Days Hours Minutes Seconds Server version CFG PEAK CURR Server address Connections Network Auditing Client tasks SHARE running Open files Server memory size Num net directories CUM Num net printers Server-busy packets Print buffer size server cache hits Receive buffers Packets Received IO buffers Watchdog terminations IO buffer size The Server status screen is a diagnostic tool that can be used to troubleshoot problems within the network and to optimize the speed at that the network runs. All the items listed on this screen are configured in other places; this screen only indicates what the current settings are. The Server status screen has some distinguishing features. The right side of the screen contains the statistics set in the Server configuration menu. These statistics are listed in three columns. The CFG column shows how the items are currently configured, the PEAK column shows how close to the configured setting each item has gotten since the network was started. The CURR setting shows the current status of each item. The PEAK and CURR numbers are dynamic, meaning any changes will immediately show on the screen. The left hand column contains information that is set when the machine is started and has cumulative information that keeps track of the total performance of the network since the network was started. Server Up-time This indicates how long the server has been running continuously since the network was loaded. Every time the network is restarted, the Server up-time figure is reset to zero. Server Version This displays the version of NetWare Lite that is currently running. The current version of NetWare Lite available is version 1.1. Server Address The server address is the node address of the network board that is installed in the server. The node address is a unique number assigned to the network board that distinguishes it from other boards on the network. This number may be set with software settings or switches on the board, or it may be built into the board. Network Auditing Network auditing has a "yes" or "no" indicator displaying whether the auditing feature has been enabled. The audit log lists such activities as logins, logouts, and backup of network management files. The date and username associated with each activity appear in the log. Network auditing can be turned on and off within the net utility in the Supervise the Network option. SHARE Running This screen lets you know whether SHARE.EXE has been loaded. SHARE is the DOS file used to control file locking and file sharing. SHARE is a necessary program to load when using a peer-to-peer network because it enables programs to be run concurrently and ensures proper file locking so two people do not access the same data file at the same time. Server Memory Size If this percentage is low, an increase of the number of IO buffers may speed up your system. Server-busy Packets This statistic informs the user of the number of times that a client resends a request to a server when the server was too busy to handle the request. A large number of server-busy packets (more than 1 percent) usually indicates that the server is not fast enough to handle the volume of requests that are being made. A third-party disk caching program will improve the speed of the server and will reduce the number of server-busy packets. Another event that will cause the server-busy packets to increase at an abnormal rate is when the server is formatting a floppy disk. DOS is not available during a disk format to service requests coming in from clients. As a result, many retries will be made from client machines causing the number of server-busy packets to increase. Server Cache Hits Percentage of requests serviced by the cache rather than accessing DOS. The cache will not be used for smaller files. If the server can service the incoming packet in one request, it will not use the cache. Usually files under 1024 bytes will not take advantage of the cache. The cache is directly related to the number and size of the IO buffers. If the percentage is low, an increase of the number of IO buffers may speed up the process. Packets Received The total number of packets received by the server. Bad Packets Received This number represents the number of times the server got a packet from the IPXODI that was damaged, possibly with a corrupt IPXODI header. Bad packets should rarely be received. If this number is non-zero, there could be a hardware problem, possibly the network board. Watchdog Terminations NetWare Lite uses a process called the watchdog to verify whether a connection exists. In a server's connection table there is a timer associated with each connection. Whenever a packet is received from a client, the timer associated with that client is reset to zero. If no packets are received within five minutes, the server calls that computer by sending out a packet asking for a response. If the client computer responds, the server will reset the timer associated with that connection. If the computer does not answer within five minutes, the server will call again once a minute for ten more minutes. If no response is received from the missing computer, the server will remove the machine from the connection table and the client will have to reestablish a connection to access the server. The process of eliminating missing connections using watchdog terminations is used to keep the connection table in each server as clean as possible. Each client machine has a connection table where the computer keeps track of how many other machines it is connected to. Unlike the server, the client's connection table is not monitored by a watchdog and will not be disconnected if the connection is lost. When a connection is lost with a server, the client machine will return the message "General failure reading device NWLite" and will prompt the user to abort, retry, or fail every time an operation that accesses the server is attempted while the server is down. When the connection is first reestablished, the user will receive the same error, but pressing <r> for retry will reestablish the connection and carry out the requested operation. Trouble Shooting with the Server Status Screen The right-hand columns of the Server status screen contain the current configuration, the peak level, and the current statistics of the items configured in the Server configuration menu with the exception of Open files. The CFG (configured) setting of Open files is the number of files that are defined in the CONFIG.SYS file that DOS uses to configure the system when booting the computer. The rest of the items have been covered previously in this document. A network administrator may use the three columns of information to fine tune the network. The items in the right hand column affect the size of the network in memory and the way the network operates. By monitoring the figures in the PEAK and CURR columns and comparing those with the number currently configured in the CFG column, a network administrator may avoid wasting valuable memory and verify that the network has plenty of room to operate. If the highest recorded value for any of these attributes approaches 80 percent of the configured setting, a network administrator should consider increasing the configured setting. Three figures need to be regularly monitored. These three are the number of connections, client tasks, and open files. As the highest values for these statistics approach or equal the corresponding configuration settings, unpredictable results can occur. These results can be anything from file locking problems, to data corruption, to the server crashing and locking the entire network. By monitoring the statistics on the Server Status Screen, a network administrator can isolate problems before they become critical, avoid wasting valuable memory space that can be better used by other applications, and tune the network so that it will operate at the most optimal level. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite Patch Release for v1.1 DOCUMENT ID#: FYI.P.6115 DATE: 05JAN93 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6106 SYMPTOM NA ISSUE/PROBLEM NetWare Lite Patch Release for v1.1 Novell has released patches that address various NetWare Lite issues. These patches can be obtained through CompuServe or through Novell directly. ***** WARNING ***** Do not apply all these patches at the same time unless directed so by technical support. CompuServe A free CompuServe membership can be obtained by dialing (800) 848-8199 in the U.S. and (614) 457-0802 outside the U.S. (ask for Representative 200). CompuServe will provide NetWare Lite users with fifteen dollars worth of credit towards online services at no charge. The files listed below are previous patches for NetWare Lite v1.1 These files are superseded by the patches in L11P02.ZIP. NWL102.ZIP L11P01.ZIP To get the files from CompuServe, do the following procedure: 1. Type GO NOVLIB 2. After you are in NOVLIB, enter into library one or library ten. 3. Download L11P02.ZIP. (This ZIP file contains the NetWare Lite patches.) You must have PKUNZIP.EXE to unzip L11P02.ZIP. If you do not have PKUNZIP.EXE, you can get it from CompuServe. It is located inside PKZ110.EXE, which is another file that must be downloaded. 4. To download PKZ110.EXE, create a directory called PKZIP (either on floppy or on your hard drive). Go to library 15 of NOVLIB and download PKZ110.EXE. Then, move PKZ110.EXE into the PKZIP directory. Type PKZ110. PKZ110.EXE will create PKUNZIP.EXE (and other programs that can be used for archiving functions). 5. After you have PKUNZIP.EXE, you can unzip L11P02.ZIP. Put L11P02.ZIP into the PKZIP directory. Next, type the following: PKUNZIP L11P02.ZIP <path where you want the files to be copied to> The patch files will be copied to the directory that you specify. Novell recommends that you copy them to a floppy diskette. This way, you will have a copy of the patches in a distinct and identifiable place. Novell If you want the patches but cannot access CompuServe, call Novell at (801) 429-5483 and request the NetWare Lite Patch Disk. It will be sent to you through U.S. mail and will take from four to seven days. The following is a list of the files that will be sent to you. (Note that these are the same files that are contained in the L11P02.ZIP file.) L11P02 DOC 7283 12-22-92 2:58p STACKFIX PAT 920 8-07-9 4:09p COMPOPEN PAT 1077 10-09-92 12:05p INT28FIX PAT 1329 10-02-92 4:28p Please note: These files have been through the patch test team. The following information is contained in the L11P02.DOC file. Included are the patch name, date, and the file that is affected by the patch (such as SERVER.EXE). Also included are problems (with accompanying symptoms) that each patch deals with. GENERAL INFORMATION You need only one SUPPORT diskette to patch all copies of NetWare Lite on your NetWare Lite network. You do not need a separate SUPPORT diskette for each copy of NetWare Lite. Make backup copies of the files before running UPATCH. Do not patch the original NetWare Lite Program and Driver diskette files. If a machine has a hard disk with NetWare Lite software, the files to be patched are in the C:\NWLITE directory. If a machine does not have a hard disk, the files to be patched are on the workstation's floppy diskette that has the NetWare Lite CLIENT.EXE. To get consistent results from the network, use UPATCH to patch all copies of NetWare Lite on the network (all servers and clients). If a server or client is not patched, it will continue with the erratic behavior that the patch is designed to correct. Review the section of this document that corresponds to the patch to find out what the patch does. Each section describes what the patch will be applied to, the patch date, the checksums, the problems the patch corrects, and the symptoms you may see before the patch is applied. You can use UPATCH to apply patches before or after running NetWare Lite; however, the changes do not take effect until the computer is rebooted and the patched files are loaded into memory. ************************************************************ ***** UPATCH INSTRUCTIONS To patch the SERVER and/or CLIENT software on a hard disk, do the following: 1. Copy each .PAT file into the NWLITE directory on the drive. 2. To apply the patch to the applicable target file, type "UPATCH" and press <Enter>. 3. When the DOS prompt appears, reboot the computer. The patched files will be used when they are loaded into memory. To patch CLIENT software on a workstation that uses a floppy diskette, do the following: 1. Insert the SUPPORT diskette into drive A: (the floppy should contain each .PAT file (applicable to the problem) and UPATCH.EXE. 2. Insert the workstation's copy of the diskette that contains CLIENT.EXE into the B: drive. Do not patch the original NetWare Lite diskettes. 3. At the DOS prompt, type A: and press <Enter>. 4. Type UPATCH B:CLIENT.EXE, press <Enter>, and follow the instructions on the screen. Note: The patches are applied to the CLIENT.EXE file and the unpatched file is retained with an .OLD file extension. If necessary, the .OLD version can be renamed and executed. 5. When the DOS prompt appears, reboot the computer. The patched CLIENT.EXE file will be used when it is loaded into memory. ************************************************************ ***** To get the latest information on NetWare Lite patches, application compatibility, hardware compatibility, upgrades and updates, top ten support issues, NetWare Lite product information, and so on, customers in the U.S. and Canada can call Novell's 24-hour automated fax service. To access this service, dial (800) NetWare [(800)638-9273] and press the star (*) key during the recorded message. ************************************************************ ***** INFORMATION ON SPECIFIC PATCHES STACKFIX.PAT NetWare Lite Server stack fix patch Target: SERVER.EXE Checksums: 558, 481, 3F0 Problem: The server switches to its DOS reentrancy stack during initialization. The Norton antivirus device driver interrupts the server after initialization and does some work. The server timer interrupts then kicks in, switches to the top of the server DOS reentrancy stack and corrupts the data that the server had on the stack before the timer interrupt. Symptoms: When the Norton antivirus device driver is loaded and SERVER.EXE attempts to load, the server will hang. ************************************************************ ***** INT28FIX.PAT NetWare Lite Client int 28 ISR patch Target: CLIENT.EXE Checksums: 765, 6DE, 641, 28C, 6DE Problem: Applications doing background printing on a NetWare Lite server/client where printing is captured to a printer connected locally may experience a server lock up. The problem requires the station to be rebooted. Each time the station is rebooted because of this problem, lost clusters are left on the hard drive. If this happens enough times without running CHKDSK /F, the FAT table will become corrupted. Symptoms: You may have this problem if you are running an application that performs background printing on a server/client with a printer connected locally and the station locks. An application that exhibits this problem is FoxPro. ************************************************************ ***** COMPOPEN.PAT Target: SERVER.EXE Problem: FCB Opens fails on read-only files. This patch inserts code that was removed from v1.0 that handles FCB opens. This patch should not be used with windows or CD-ROMs. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Lite Update Release for v1.1 DOCUMENT ID#: FYI.P.6116 DATE: 05JAN93 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM NetWare Lite Update Release for v1.1 Novell has released updates that address NetWare Lite issues. These updates can be obtained through CompuServe or through Novell directly. Note: It is recommended that all installations of NetWare Lite v1.1 acquire and install all the files contained in L11U01.ZIP. CompuServe A free CompuServe membership can be obtained by dialing (800) 848-8199 in the U.S. and (614) 457-0802 outside the U.S. (ask for Representative 200). CompuServe will provide NetWare Lite users with fifteen dollars worth of credit toward online services at no charge. To get the files from CompuServe, do the following procedure: 1. Type GO NOVLIB 2. After you are in NOVLIB, enter into library one or library ten. 3. Download L11U01.ZIP. (This ZIP file contains the NetWare Lite patches.) You must have PKUNZIP.EXE to unzip L11U01.ZIP. If you do not have PKUNZIP.EXE, you can get it from CompuServe. It is located inside PKZ110.EXE, which is another file that must be downloaded. 4. To download PKZ110.EXE, create a directory called PKZIP (either on floppy or on your hard drive). Go to library 15 of NOVLIB and download PKZ110.EXE. Then, move PKZ110.EXE into the PKZIP directory. Type PKZ110. PKZ110.EXE will create PKUNZIP.EXE (and other programs that can be used for archiving functions). 5. After you have PKUNZIP.EXE, you can unzip L11U01.ZIP. Put L11U01.ZIP into the PKZIP directory. Next, type the following: PKUNZIP L11U01.ZIP <path where you want the files to be copied to> The patch files will be copied to the directory that you specify. Novell recommends that you copy them to a floppy diskette. This way, you will have a copy of the patches in a distinct and identifiable place. Novell If you want the patches but cannot access CompuServe, call Novell at (801) 429-5483 and request the NetWare Lite Patch Disk. It will be sent to you through US Mail and will take from four to seven days. The following is a list of the files that will be sent to you. (Note that these are the same files that are contained in the L11U01.ZIP file.) L11U01.DOC 8121 12-21-92 11:22p GETATRIB.PAT 1248 12-03-92 9:09a CLOSEFIL.PAT 1084 12-01-92 10:30a LPTSTAT.PAT 1255 11-16-92 2:06p RECONFIX.PAT 2626 10-12-92 9:52a CLPRINTR.PAT 1198 11-16-92 10:12a INFORMATION ON SPECIFIC PATCHES GETATRIB.PAT NetWare Lite Client get file attribute fix patch Target: CLIENT.EXE Checksums: 758, BB2, 59A, 351, BB2 Problem: When running the Quicken finance software and printing to a NetWare Lite captured printer, the Quicken printing fails with the "Can't print to LPT1" message. Symptoms: Quicken printing fails with the "Can't print to LPT1" message. This also fixes the problem with getting file attributes across the network. The problem was with OPENDEV.PAT. ************************************************************ ***** CLOSEFIL.PAT NetWare Lite v1.1 Server close file handles fix patch Target: SERVER.EXE Checksums: 2CC, 2B4, 20 Problem: When a client station has open files on a NetWare Lite server and the client reboots with the files still open, sometimes the files will not be closed when the client reconnects or when watchdog clears the station connection. Symptoms: Files are left open on the server when a client reboots. ************************************************************ ***** LPTSTAT.PAT NetWare Lite v1.1 Server LPT printer status fix patch Target: SERVER.EXE Checksums: 5B7, CO1, 575, 307, C01 Problem: Print jobs in NetWare Lite are being sent to a printer that has been taken offline or powered off. The jobs are being lost. Symptoms: Print jobs are being lost when the printer has been powered off or taken offline. ************************************************************ ***** RECONFIX.PAT NetWare Lite Client reconnect patch Target: CLIENT.EXE Checksums: 76A, 74F, 10EF, 66A, 64F, 8F7, 3A3, 3A3, 10EF Problem: The reconnection between server and client fails to occur when the NET CAPTURE or NET PRINT commands are issued by a client to a server that has just been rebooted. Subsequent NET CAPTURE or NET PRINT commands from the client station will work normally. Symptoms: When using the NET CAPTURE or NET PRINT commands as the first commands from a client to a server that has just been rebooted, the error messages "Redirect device -- Too many open files." or "Write file -- Access denied." will be displayed and the command will fail. ************************************************************ ***** CLPRINTR.PAT NetWare Lite Client printer corruption fix patch Target: CLIENT.EXE Checksums: 6AC, 562, 5D4, 316, 562 Problem: Running certain applications on a client/server with a local printer will produce printer output that has been corrupted. Symptoms: Printer output that has been captured through NetWare Lite will be corrupted. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Troubleshooting Lockup (Hanging) Problems DOCUMENT ID#: FYI.P.6086 DATE: 26JAN93 PRODUCT: NetWare Lite PRODUCT VERSION: All versions SUPERSEDES: FYI.P.6074 SYMPTOM NA ISSUE/PROBLEM Troubleshooting Lockup (Hanging) Problems While using a networking system, problems may be met; locking could be one of them. This document, which is divided into two areas of hardware and software, is intended to help diagnose and resolve lockup problems. Hardware 1. Most Local Area Network (LAN) boards come with the ability to change the interrupt line, base I/O address, and memory address settings (in some cases). This is done by either setting switches located on the network board or through a software setup utility. When NetWare Lite is installed, it must be told what the interrupt line, base I/O, and the memory address settings are on the board. If the board does not agree with the settings that the network is searching for, it could cause lockups. This usually happens when the network board driver is loaded, when SERVER.EXE is loaded, when CLIENT.EXE is loaded, or when the NET utility is used. The solution for this type of problem is straight forward. The settings on the board need to be determined by checking the switches and sometimes cross referencing it with the documentation provided with the network board. After they are found, the install process is repeated for NetWare Lite and the correct options chosen to correspond to the hardware. 2. Another lockup problem may occur when the interrupt line, base I/O address, or memory address conflict with another device in the same machine. Each of these settings must be unique to the network board. Devices that may conflict include modems or mice. Lockups in this case can show up anytime after the network has been loaded. A reference list is provided that contains the interrupt line and Base I/O address for many devices. For more information on interrupts, see Fax Document 212 or FYI.P.6054. (Call 1-800-NET-WARE and press the * key during the initial recording.) ┌───────────────────┬────┬──────────────────┐ │ Options │IRQ │ Base I/O │ ├───────────────────┼────┼──────────────────┤ │ Com1 │ 4 │ 3F8-3FF │ │ Com2 │ 3 │ 2F8-2FF │ │ LPT1 │ 7 │ 378-37F │ │ LPT2 │ 5 │ 278-27F │ │ VGA │ 2 │ 3C0-3CF │ │ EGA │ 2 │ 3C0-3CF │ │ CGA │ │ 3D0-3DF │ │ Hercules │ │ 3B4-3BF │ │ Mono │ │ 3B0-3BF │ │ AT controller │ 14 │ 1F0-1F8, 170-177 │ │ Floppy controller │ 6 │ 1F0-1F8, 3F0-3F7 │ │ Tape controller │ 5 │ 280-28F │ │ XT controller │ 5 │ 320-32F │ │ │ │ │ └───────────────────┴────┴──────────────────┘ Note: Along with the above mentioned I/O address conflicts, address 360 should be avoided. This address may overlap with beginning address 378 that is used in LPT1 processes. (This is hardware defined and may depend on the particular network board used.) The best solution for this is to configure the network board I/O address at 300, 320, or 340. These settings will work for most systems. 3. The switch settings on the board are not the only things that can cause problems. Some network boards, when not fully compatible with Novell certified boards, can also cause problems. When locking problems do not seem related to any of the settings on the board, try using a different board to see if it does clear up. Occasionally, a bad board is run across. Software 1. Some software can cause a lockup when it is simply not compatible with NetWare Lite. These programs usually use protocol that tries to print, gain access to RAM, or gain access to the hard drive without going through DOS. Because NetWare Lite is written to work with DOS these programs cannot be used. 2. NetWare Lite is a memory resident program that occupies part of RAM. This limits the amount of room allowed for other programs. When conventional memory is too low, it can cause applications to crash. One solution for this is to load as much as possible into upper memory. Out of the files loaded through the STARTNET.BAT file, all but SERVER.EXE can be loaded high. This is done in MS-DOS 5.0 by putting "LOADHIGH" before the file name to be loaded. This is done in DR-DOS 6.0 by putting "HILOAD" before the file name to be loaded. (Third-party memory managers may also be used but not loaded at the same time with other memory managers.) Note that many memory resident programs can be loaded high but others cannot. If you load a particular program high and find that your system locks more frequently, load it back into conventional memory again. Example for loading most of STARTNET.BAT high using MS-DOS format: loadhigh lsl loadhigh ne2000 loadhigh ipxodi a loadhigh share server loadhigh client 3. Some network boards use upper memory for their own processes that range from C000h to E000h. If this is the case, they do not require a memory manager to control them. Furthermore, this area in upper memory should be excluded from the memory manager's control. To do so, insert the following in CONFIG.SYS: For MS-DOS 5.0 use: device=c:\DOS\emm386.exe x=mmmm-nnnn For DR-DOS 6.0 use: device=c:\drDOS\emm386.sys /exclude=mmmm-nnnn (mmmm is beginning and nnnn is the ending address.) Note: Most network-board drivers occupy about 8 to 16 KB of memory. Check the references for your specific device. 4. CONFIG.SYS also has a parameter that can be changed that may cause computers to lock. That is "files=xx." The xx is the number of files that machine can have open at one time. The suggested amount is 10 files per client plus 30 more. 5. Along the same line as the above paragraph, the number of client tasks could have the same effect. To change the client tasks you must run the NET utility, go to "supervise the network," then "server configuration." This parameter is normally set between 5 and 10 per client. 6. Terminate-Stay-Resident (TSR) programs can also cause lockups. They can show up in several ways of which most commonly is when the TSR is functioning. It can also happen when the TSR seems inactive. The easiest way to find out if a TSR is causing the lockup is by renaming AUTOEXEC.BAT and CONFIG.SYS and then putting the following in the CONFIG.SYS: FILES=30 LASTDRIVE=G If the problem no longer persists, add each component back into AUTOEXEC.BAT and CONFIG.SYS one by one until you find the one that is causing the problem. Modifications may be necessary to make the conflicting TSR work properly, or it may even be incompatible with the network environment. 7. Some incompatibilities have been found with certain hardware and software configurations. NetWare Lite has made some modification to adapt to these systems. These modifications come in the form of a patch that is applied once to each machine in the network. More specifics on these patches can be faxed to you through NetWare Lite's automated Fax Document 263 or see FYI.P.6087. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Upload of L11U01.ZIP DOCUMENT ID#: FYI.P.10963 DATE: 29DEC92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM NA ISSUE/PROBLEM Concerning the file L11U01.ZIP available on available on NetWire or NetWare Express. For NetWare Lite v1.1. Files included: GETATRIB.PAT 1248 12-03-92 9:09a CLOSEFIL.PAT 1084 12-01-92 10:30a LPTSTAT.PAT 1255 11-16-92 2:06p RECONFIX.PAT 2626 10-12-92 9:52a CLPRINTR.PAT 1198 11-16-92 10:12a INFORMATION ON SPECIFIC PATCHES GETATRIB.PAT - NetWare lite Client get file attribute fix patch Target: CLIENT.EXE Checksums: 758, BB2, 59A, 351, BB2 Problem: When running the Quicken finance software and printing to a NetWare Lite captured printer, Quicken printing fails with the message "Can't print to LPT1." Symptoms: Quicken printing fails with the message "Can't print to LPT1". This also fixes the problem with getting file attributes across the network. The problem was with OPENDEV.PAT. CLOSEFIL.PAT - NetWare Lite v1.1 Server close file handles fix patch Target: SERVER.EXE Checksums: 2CC, 2B4, 20 Problem: When a client station has open files on a NetWare Lite server and the client reboots with the files still open, sometimes the files will not be closed when the client reconnects or when watchdog clears the station connection. Symptoms: Files are left open on the server when a client reboots. LPTSTAT.PAT - NetWare Lite v1.1 Server LPT printer status fix patch Target: SERVER.EXE Checksums: 5B7, CO1, 575, 307, C01 Problem: Print jobs in NetWare Lite are being sent to a printer that has been taken off line or powered off. The jobs are being lost. Symptoms: Print jobs are being lost when the printer has been powered off or taken off line. RECONFIX.PAT - NetWare Lite Client reconnect patch Target: CLIENT.EXE Checksums: 76A, 74F, 10EF, 66A, 64F, 8F7, 3A3, 3A3, 10EF Problem: The reconnection between server and client fails to occur when the NET CAPTURE or NET PRINT commands are issued by a client to a server that has just been rebooted. Subsequent NET CAPTURE or NET PRINT commands from the client station will work normally. Symptoms: When using the NET CAPTURE or NET PRINT commands as the first commands from a client to a server that has just been rebooted, the error messages "Redirect device -- Too many open files." or "Write file -- Access denied." will be displayed and the command will fail. CLPRINTR.PAT - NetWare Lite Client printer corruption fix patch Target: CLIENT.EXE Checksums: 6AC, 562, 5D4, 316, 562 Problem: Running certain applications on a client/server with a local printer will produce printer output that has been corrupted. Symptoms: Printer output that has been captured through NetWare Lite will be corrupted. SOLUTION NA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: No DOS ODI Drivers for DEC Ethernet LAN Boards DOCUMENT ID#: FYI.P.09062 DATE: 11JUN92 PRODUCT: NetWare Lite PRODUCT VERSION: v1.0 SUPERSEDES: FYI.P.07850 SYMPTOM NA ISSUE/PROBLEM Are Open Data-Link Interface (ODI) drivers available for the following Digital Equipment Corporation (DEC) Ethernet LAN boards? DE100, DE200, DE210, DE201, or DE202 The user wanted ODI drivers for NetWare Lite software. SOLUTION Yes. Refer to the following Novell Labs reports: l-1057 DE-100 (NetWare v3.11 Only) l-1058 DE-101 l-1059 DE-200 l-1060 DE-201 l-1061 DE-202 l-1062 DE-210 ODI Drivers should be used with NetWare Lite. Using dedicated IPX drivers with NetWare Lite software is not officially supported by Novell. If forced to use a dedicated IPX driver in NetWare Lite software, do the following: 1. Select the appropriate LAN driver during the installation. 2. Edit the STARTNET.BAT file so that it loads the desired IPX.COM (then SHARE, SERVER, CLIENT) instead of Link Support Layer (LSL), <odi mlid>, and IPXODI. 3. Also if it is necessary to load IPX with a different configuration, then change the NET.CFG file created during the install to reflect that change.